-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
modules/nixos/buildbot-repo-allowlist: add microvm.nix #1598
base: master
Are you sure you want to change the base?
Conversation
6ca7533
to
d58f537
Compare
modules/nixos/buildbot.nix
Outdated
"astro/microvm.nix" = { | ||
url = "https://github.com/qowoz/microvm.nix.git"; | ||
defaultBranch = "main"; | ||
}; |
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.
"astro/microvm.nix" = { | |
url = "https://github.com/qowoz/microvm.nix.git"; | |
defaultBranch = "main"; | |
}; | |
"astro/microvm.nix" = { | |
url = "https://github.com/qowoz/microvm.nix.git"; | |
defaultBranch = "main"; | |
evalWorkerCount = 4; | |
}; |
@Mic92 Could we make evalWorkerCount configurable per repo? This repo uses a lot of memory and I really don't want to have to reduce it just for one repo.
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.
@zowoq sounds doable and useful. Please open an issue. We have most of the code needed for this to happen already there.
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 found it was easy to add it as a config file option so for now I'll use that: nix-community/buildbot-nix@2d039c3
Unfortunately found other problems. Even with just 8 workers it still uses a lot of memory, too much considering that we other jobs running. Also very slow to eval, after 20 minutes it hasn't even finished aarch64-linux, it'll block jobs other repos. Not sure if we'd want change the current eval lock to something like a per repo eval lock and limit the buildbot instance to 2 concurrent evals.
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.
How many virtual machines does this have?
@astro are you sharing nixpkgs instances in your microvm machines tests. Do you disable documentation? Are you applying many overlays?
Maybe we also need to make configurable what it evaluates i.e. only a single architecture.
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 can easily get the test matrix above 128 tests. It's all individual flake check entries but the nixpkgs are pinned through flake.lock. microvm.nix overlay only.
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.
hyperfine -r 5 'nix-eval-jobs --workers 1 --force-recurse --flake github:astro/microvm.nix#hydraJobs.x86_64-linux.crosvm-startup-shutdown'
Benchmark 1: nix-eval-jobs --workers 1 --force-recurse --flake github:astro/microvm.nix#hydraJobs.x86_64-linux.crosvm-startup-shutdown
Time (mean ± σ): 91.982 s ± 0.193 s [User: 54.372 s, System: 25.974 s]
Range (min … max): 91.669 s … 92.138 s 5 runs
hyperfine -r 5 'nix-eval-jobs --workers 1 --force-recurse --flake github:astro/microvm.nix#hydraJobs.aarch64-linux.qemu-9pstore-overlay-shutdown-command'
Benchmark 1: nix-eval-jobs --workers 1 --force-recurse --flake github:astro/microvm.nix#hydraJobs.aarch64-linux.qemu-9pstore-overlay-shutdown-command
Time (mean ± σ): 92.361 s ± 0.502 s [User: 54.808 s, System: 26.118 s]
Range (min … max): 91.557 s … 92.925 s 5 runs
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.
Seems I only pasted the benchmarks and forgot to include a comment.
I found that lots of the hydraJobs attributes took around 90 seconds each to eval.
The combination of the number of tests, the test attributes are slow to eval and that they also use a significant amount memory is a problem. I need to limit the number of parallel evals to reduce memory usage, which then makes the overall eval time to slow to be practical.
Good news is that soon we'll be able to offer buildbot CI app to external repos so if we can address eval issues you could have PR tests without needing to move the repo into nix-community.
@@ -0,0 +1,23 @@ | |||
[ | |||
"qowoz/microvm.nix" | |||
"nix-community/authentik-nix" |
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.
Isn't the github topic less work overall than having this list synchronously managed?
Didn't start automatically so I triggered an eval manually:
qowoz/microvm.nix@4843601
seems to ignore buildbot-nix.toml, works after the flake is changed to checksseems to have been fixed in buildbot-nixeval uses a massive amount of memory