-
-
Notifications
You must be signed in to change notification settings - Fork 15.2k
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
tectonic: add online passthru.tests.biber-compatibility #278410
Conversation
97ccc2d
to
7d8a3b4
Compare
476f68a
to
1ce6561
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.
Nit.
1ce6561
to
fe4860f
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.
Commit message: passthru.tests.biber-compatibility
Ah yes, of course hahaha totally missed it 😆 fixed. |
fe4860f
to
e3570b9
Compare
Great, should be good to go when CI is green. Ping me if I forget. |
The test requires internet access to fetch tectonic's web bundle on demand. This is achieved by abusing a fixed-output derivation, which is capable of internet access. The `tectonic.outPath` is included in the test package name. This ensures that it is always triggered for rebuild when the main derivation changes. Co-authored-by: Doron Behar <[email protected]>
e3570b9
to
58627fa
Compare
Splendid! Thank you! Just fixed |
Description of changes
Implement the (LaTeX + biber) compile test for the tectonic package wrapped with biber.
tectonic.outPath
is included in the test package name. This ensures that it is always triggered for rebuild when the main derivation changes.I do have a few concerns about doing this:
tectonic.passthru.tests
be triggered by hydra? Everystaging-next
build would probably change tectonic's outPath, which will change the test's name according to this current design. I am not sure (1) whether this would trigger a test rebuild in hydra, and (2) if this happens, whether it would lead to too many test rebuilds. I don't want to accidentally DDoS the upstream server!fetchurl
. Is that legal in nixpkgs?This PR follows from discussions in #273740. Note, however, that this PR is independent of the previously discussed web-bundle-locking proposal (which I am also working on upstream, but independent of this PR).
Update:
nixpkgs-review
as it causes zero rebuild of the main packages.x86_64-*
and*-linux
(log), still pending onaarch64-darwin
.Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.