Uh oh!
There was an error while loading. Please reload this page.
fs: move rmSync implementation to c++ - #53617
Conversation
c541155 to
3d2975dCompare
This comment was marked as outdated.
This comment was marked as outdated.
3d2975d to
d820ac1Comparenodejs-github-bot
commented
Jun 28, 2024
d820ac1 to
8d02638CompareUh oh!
There was an error while loading. Please reload this page.
8d02638 to
2538925Comparebenjamingr
commented
Jun 28, 2024
Benchmark results (since CI is locked down): |
Uh oh!
There was an error while loading. Please reload this page.
Failed to start CI⚠ Something was pushed to the Pull Request branch since the last approving review. ✘ Refusing to run CI on potentially unsafe PRhttps://github.com/nodejs/node/actions/runs/9784060111 |
nodejs-github-bot
commented
Jul 17, 2024
nodejs-github-bot
commented
Jul 17, 2024
anonrig
commented
Jul 17, 2024
cc @nodejs/cpp-reviewers can you review? |
nodejs-github-bot
commented
Jul 18, 2024
Landed in 7168295 |
aduh95
commented
Jul 21, 2024
Marking it as dont-land because of #53962 (comment) |
anonrig
commented
Jul 21, 2024
@richardlau@aduh95 any idea why the tests are flaky? |
aduh95
commented
Jul 21, 2024
@anonrig the flakiness of the test (and its root cause) is beside the point, the fact that it break something is our CI means it likely going to break our users and therefore should not land on release lines. In an ideal world, when the CI reports the same test failing 6 times in the same PR but is passing in others, that PR would not land until the flakiness is addressed. |
anonrig
commented
Jul 21, 2024
Yes, I agree. I'm trying to understand how this change caused this regression. |
targos
commented
Jul 28, 2024
Is this safe to land on v22.x with cf2bce6 ? |
I need to write some benchmarks before making this pull-request ready.
Benchmark on all
fscommands: https://ci.nodejs.org/view/Node.js%20benchmark/job/benchmark-node-micro-benchmarks/1575/