-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cagebreak: 1.6.0 -> 1.7.0 #119963
cagebreak: 1.6.0 -> 1.7.0 #119963
Conversation
But in this one I got an actual backtrace with
|
Result of 1 package built:
|
Result of 1 package built successfully:
1 suggestion:
|
@Synthetica9 IIRC cagebreak will crash on startup if the config file is missing (poor UX choice imo) |
Oh, yeah, that's very poor UX, but thanks for the heads-up |
3c41551
to
651aa2d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You might be already on it but could you also rebase to resolve the merge conflict and limit the test to x86_64-linux
(28b8cff#diff-307c155c790abf7b54b5dec19dc230c6d692c6dca0604760d8389c7aed543c10R50)?
651aa2d
to
5386cb9
Compare
Yesterday I had a brief look at this and got the following output for
The first message ( Starting Cagebreak directly is likely the best solution but I haven't looked much into Wayland tests so far (wanted to investigate manually logging in via a VT/tty for a Sway test but never got around to that). Note: I'll rebase this PR to resolve the merge conflict (2da39dd). |
Motivation for this change
Tests still failing, related to the failure in #119615
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)