nixpkgs-unstable release channel 2-4 days out-of-sync from hydra

[jonringer]

According to hydra, "trunk" has been building regularly: https://hydra.nixos.org/job/nixpkgs/trunk/unstable#tabs-constituents

However, according to https://howoldis.herokuapp.com/ it's 2 days old.

And this is verified by going to https://nixos.org/channels/nixpkgs-unstable which redirects to https://releases.nixos.org/nixpkgs/nixpkgs-20.09pre214374.1fe82110feb at the time of writing.

But if we go to the read-only channel repo: https://github.com/NixOS/nixpkgs-channels/tree/nixpkgs-unstable it says it's 4 days old

[jonringer]

While researching for this issue, I noticed that trunk on hydra was held up by chromium.aarch64 https://hydra.nixos.org/eval/1572374 , specifically https://hydra.nixos.org/build/113412855

I think it might be worth while to have a discussion about packages which take obscene amounts of time to compile (most likely to be aarch64 jobs). The https://hydra.nixos.org/build/113412855 job is currently referenced in 15 evaluations, which means that it's been roughly 60 hours since it was first evaluated.

[jonringer]

cc @grahamc @FRidh @worldofpeace

[thefloweringash]

Related https://github.com/NixOS/nixpkgs/pull/78347

[stale[bot]]

Hello, I'm a bot and I thank you in the name of the community for opening this issue.

To help our human contributors focus on the most-relevant reports, I check up on old issues to see if they're still relevant. This issue has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

The community would appreciate your effort in checking if the issue is still valid. If it isn't, please close it.

If the issue persists, and you'd like to remove the stale label, you simply need to leave a comment. Your comment can be as simple as "still important to me". If you'd like it to get more attention, you can ask for help by searching for maintainers and people that previously touched related code and @ mention them in a comment. You can use Git blame or GitHub's web interface on the relevant files to find them.

Lastly, you can always ask for help at our Discourse Forum or at #nixos' IRC channel.

[jonringer]

closing, issue seems to be related to either aarch or darwin taking a long time to munch through a package set