You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a hledger release, I search for nix builds at https://hydra.nixos.org/search?query=hledger. This eventually produces a long list of jobs (which I ignore) and then two lists of builds, each with a "The following builds match your query:" heading. They look similar but not quite the same. I wonder why there are two lists ?
The text was updated successfully, but these errors were encountered:
simonmichael
changed the title
Multiple "The following builds match your query" sections ?
Two "The following builds match your query" lists ?
Dec 6, 2019
Hi Simon, a quick read of the source reveals the following explanation:
The build search results are rendered here. Note that there are two calls of the renderBuildSearch template defined above corresponding to the two lists of builds you see.
Note that renderBuildSearch defaults to rendering the data in builds. However the second call overrides builds with buildsdrv.
The results are computed here. As you can see builds contains builds with an output path that matches your query while buildsdrv contains builds with a derivation path that matches your query.
It would be better if the template would describe this difference by returning something like:
The output paths of the following builds match your query
and:
The derivation paths of the following builds match your query
Care to submit a PR for that?
dasJ
added a commit
to helsinki-systems/hydra
that referenced
this issue
Feb 24, 2020
After a hledger release, I search for nix builds at https://hydra.nixos.org/search?query=hledger. This eventually produces a long list of jobs (which I ignore) and then two lists of builds, each with a "The following builds match your query:" heading. They look similar but not quite the same. I wonder why there are two lists ?
The text was updated successfully, but these errors were encountered: