Backport breakpointHook [18.09] #49099
Merged
+60
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(cherry picked from commit 84e915a)
Usuage: Add breakpointHook to your `buildInputs` like this:
stdenv.mkDerivation rec {
# ...
buildInputs = [ breakpointHook ];
});
When the build fails as show in this example:
pkgs.hello.overrideAttrs (old: {
buildInputs = [ breakpointHook ];
postPatch = ''
false
'';
});
It will halt execution printing the following message:
build failed in patchPhase with exit code 1
To attach to this build run the following command as root:
cntr attach -t command cntr-/nix/store/ynyb4n82x2r7sldd58pbb405jdqh5f00-hello-2.10
Installing cntr and running the command will provide shell access to the
build sandbox of failed build:
sudo cntr attach -t command cntr-/nix/store/ynyb4n82x2r7sldd58pbb405jdqh5f00-hello-2.10
WARNING: bad ownership on /nix/var/nix/profiles/per-user/root, should be 1000
[nixbld@localhost:/var/lib/cntr]$
At /var/lib/cntr the sandbox filesystem is mounted. All commands and
files of the system are still accessible within the shell.
To execute commands from the sandbox use the `cntr exec` subcommand.
(cherry picked from commit f10b935)
(cherry picked from commit 325a569)
GrahamcOfBorg
added
8.has: documentation
|
Success on aarch64-linux (full log) Attempted: breakpointHook The following builds were skipped because they don't evaluate on aarch64-linux: cntr Partial log (click to expand)
|
|
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: breakpointHook, cntr Partial log (click to expand)
|
|
Success on x86_64-linux (full log) Attempted: breakpointHook, cntr Partial log (click to expand)
|
LnL7
reviewed
Oct 26, 2018
doc/stdenv.xml
Outdated
| This hook will make a build pause instead of stopping | ||
| when a failure happen. It prevents nix to cleanup the build | ||
| environment immediatly and allows the user to attach | ||
| to a build environemnt using the <varname>cntr</varname> command. |
There was a problem hiding this comment.
<command> is probably better suited for this
(cherry picked from commit 7f80fb2)
|
Success on aarch64-linux (full log) Attempted: breakpointHook The following builds were skipped because they don't evaluate on aarch64-linux: cntr Partial log (click to expand)
|
|
Success on x86_64-linux (full log) Attempted: breakpointHook, cntr Partial log (click to expand)
|
|
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: breakpointHook, cntr Partial log (click to expand)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation for this change
Things done
sandboxinnix.confon non-NixOS)nix-shell -p nox --run "nox-review wip"./result/bin/)nix path-info -Sbefore and after)