tools: update nixpkgs-unstable to ab72be9733b41190ea34f1422a3e4e243ed#62821
tools: update nixpkgs-unstable to ab72be9733b41190ea34f1422a3e4e243ed#62821nodejs-github-bot merged 1 commit intomainfrom
Conversation
8fc5df6 to
dd8f89c
Compare
|
Removed the revert of numtide/treefmt@b96016b now that the fix has landed upstream (tested on https://github.com/nodejs/node-auto-test/actions/runs/24636421675). Also bumped the version to one with |
dd8f89c to
9822fa1
Compare
Signed-off-by: Filip Skokan <panva.ip@gmail.com>
9822fa1 to
bd9ab76
Compare
aduh95
left a comment
There was a problem hiding this comment.
Does it make sense for you to sign off something you did not author?
|
rebase from main changed the commit to me as the author, for some reason, so by policy i must sign off 😀. do you want to close this and trigger a fresh sync instead, or just tell me how to proceed. |
|
Landed in 3e32a13 |
|
Interestingly, the intermittent lint-nix timeouts appear to have recurred since this commit. |
|
I did another test:
13 timeout over 512 runs is roughly 2.5%, which is not nothing, but all things considered 97.5% of reliability is a pretty high score for a Node.js CI :p In numtide/treefmt#677 (comment), I have found very different figures, so I wonder if there's something else affecting the reliability. |
Signed-off-by: Filip Skokan <panva.ip@gmail.com> PR-URL: #62821 Reviewed-By: Filip Skokan <panva.ip@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
This is an automated update of nixpkgs-unstable to ab72be9733b41190ea34f1422a3e4e243ed.