| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
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 openssl_4_0 |
Sorry, something went wrong.
Signed-off-by: Filip Skokan <panva.ip@gmail.com>
There was a problem hiding this comment.
Does it make sense for you to sign off something you did not author?
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
|
I see no reason to close this, I'm asking to try to avoid having to do that in the future. Not that the rebase did not change the authorship, you were already set as author of 8fc5df6. I've opened #62856 to address this. |
Sorry, something went wrong.
|
Interestingly, the intermittent lint-nix timeouts appear to have recurred since this commit. |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
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>
| Back | FazBrowse Home | New Git URL |
This is an automated update of nixpkgs-unstable to ab72be9733b41190ea34f1422a3e4e243ed.