-
-
Notifications
You must be signed in to change notification settings - Fork 15.3k
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
systemd timeout arguments to use infinity instead of 0 #50934
Conversation
Oh, nice catch. While we're at it, it should also be fixed for:
|
95475bc
to
76d412a
Compare
@c0bw3b Could you take another look? Unfortunately I was unable to verify the google cloud environment image creation. |
LGTM. @rbvermaa @zimbatm @AmineChikhaoui to review the change on |
@GrahamcOfBorg test cloud-init |
No attempt on aarch64-linux (full log) The following builds were skipped because they don't evaluate on aarch64-linux: tests.cloud-init Partial log (click to expand)
|
No attempt on x86_64-linux (full log) The following builds were skipped because they don't evaluate on x86_64-linux: tests.cloud-init Partial log (click to expand)
|
@GrahamcOfBorg build nixosTests.cloud-init |
Success on x86_64-linux (full log) Attempted: nixosTests.cloud-init Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: nixosTests.cloud-init Partial log (click to expand)
|
@c0bw3b thank you for the review. Should this target |
This is good as-is targeting the A "mass-rebuild" is when hundreds of packages need to be rebuilt after a shared component is changed. |
thanks @cyounkins ! I double-checked and didn't find any more instances |
Fixes #49700
Motivation for this change
systemd changed the behavior for TimeoutStartSec in 229.
infinity
is now the preferred argument to disable timeouts.Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)