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
Nixos test containers python port #74218
Conversation
@GrahamcOfBorg test containers-bridge containers-ipv4 containers-ipv6 |
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.
As all of these are very similar, what do you think about joining the network-related ones into a single testScript
, and testing each variant in a subtest?
nixos/tests/containers-ipv4.nix
Outdated
chomp $ip; | ||
$machine->succeed("ping -n -c1 $ip"); | ||
$machine->succeed("curl --fail http://$ip/ > /dev/null"); | ||
with subtest("wait 2s for container to start and network to be up"): |
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.
I think we shouldn't overdo with grouping things into subtests. This should really be just a comment. ;-)
e528601
to
1479e03
Compare
@GrahamcOfBorg test containers-bridge containers-ipv containers-imperative |
1479e03
to
f58088c
Compare
@GrahamcOfBorg test containers-bridge containers-ip containers-imperative |
f58088c
to
b1e9e7c
Compare
@GrahamcOfBorg test containers-bridge containers-ip containers-imperative |
b1e9e7c
to
9de0a8a
Compare
@GrahamcOfBorg test containers-bridge containers-ip containers-imperative |
Motivation for this change
#72828
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @flokli @worldofpeace @Lassulus