Another question regarding broken packages

[gurkan]

Hi there
I’ve just upgraded to 20.03, but apparently one of the packages I use (and maintain) marked as broken on 20.03 branch, but not on master.
I failed to find or reproduce the issue, so I have some questions:

• How can I trace this commit back to the hydra job/jobset (I assume) which decided it was broken?
• I’ve allowed broken packages on my system and it built/worked correctly:
  • Should I just wait for a new evaluation (which would also automatically remove broken meta)?
  • If it won’t happen automatically (ಠ_ಠ) shall I open a PR/issue?

Thanks, and double thanks for all the work, 20.03 looks rad

[worldofpeace]

I’d send you link to ZERO HYDRA FAILURE, which had details on the issue, but it seems GitHub is having some issues so I’ll just reiterate here.

@gurkan

How can I trace this commit back to the hydra job/jobset (I assume) which decided it was broken?

Each package will have a job on hydra:

• Hydra - nixos:release-20.03 (release-20.03)
• Hydra - nixos:trunk-combined (master)

However, exploring hydra UI can be slow so example urls for a package would be like:

• Hydra - nixos:release-20.03:nixpkgs.bash.x86_64-linux (release-20.03)
• Hydra - nixos:trunk-combined:nixpkgs.bash.x86_64-linux (master)

@gurkan

I’ve allowed broken packages on my system and it built/worked correctly:

• Should I just wait for a new evaluation (which would also automatically remove broken meta)?
• If it won’t happen automatically (ಠ_ಠ) shall I open a PR/issue?

This isn’t automatic “yet”, so you can open a PR removing the attribute against the release-20.03 branch.

[gurkan]

Yep, hydra UI is a bit painful But thanks for all the info I’ll dig around and open a PR for (hopefully multiple) false-positives.