-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
How to reproduce jobs locally? -> improve logs #671
Comments
Related, though not exactly the same as your question: I'd love an easy, one-shot way to run an entire hermetic environment exactly equal to the ofborg runners that run as nixos/nixpkgs CI. E.g. a full nixos config so you can repro CI failures locally and iterate on it before pushing a fix. |
I agree this would be very helpful.
Additionally, it seems GitHub doesn't show the |
Most of the commands ofBorg runs can be seen with proper tokenization in the code here: ofborg/ofborg/src/tasks/eval/nixpkgs.rs Lines 433 to 562 in eb120ff
|
I just had a failing instance of
ofborg-eval-lib-tests
: https://gist.github.com/GrahamcOfBorg/85196b733b08a4c1c29909c2a1a5af42... and I'm having a hard time trying to debug this.
Several things are missing here:
ofborg-eval-lib-tests
in either nixpkgs or nixos/ofborg leads to zero results. Where is the job defined?All of the above should be easy fixes and would make debugging this stuff a lot easier.
EDIT: I just noticed that it displays the command in github next to the job. So that helps. But still it would be nice to have this clearly stated in the logs as well. Also the command displayed in github
nix-build --arg pkgs 'import ./. {}' ./lib/tests/release.nix
doesn't actually seem to work and fails with:The text was updated successfully, but these errors were encountered: