Failing on Node.js Windows "current"

[rvagg]

Some unicode filename thing that's now popping up, either Node.js latest change or something to do with the Windows deployment in CI: https://github.com/ipld/codec-fixtures/actions/runs/5756528910/job/15606085523

[SgtPooki]

Looks like the last successful job here was https://github.com/ipld/codec-fixtures/actions/runs/5458983079/job/14778794547 running against 239f3b0

[SgtPooki]

Diff of repo between action runs: 239f3b0...01ec64d

• NodeJS passing: 20.3.1
  
• NodeJS failing: 20.5.0

Some other details:

• Dependency install / setup has actually been broken for a while? https://github.com/ipld/codec-fixtures/actions/runs/5458983079/job/14778794547#step:4:9

[rvagg]

Dependency install / setup has actually been broken for a while

hah, escaping, how does it even work? https://github.com/ipld/codec-fixtures/blob/master/.github/workflows/cron.yml#L28

Last successful run you identified has a date of Jul 5, which coincides with the Node.js 20.4.0 release, same day, so subsequent runs would be picking up that new one as "current" and failing. So it's something in that release that has messed up Windows: https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md#2023-07-05-version-2040-current-rafaelgss

[rvagg]

Arrr, thar she is: nodejs/node#48673, fixed in libuv/libuv#4092, but needs a release of libuv and Node to get it fixed here. Well that takes the pressure off, but failures aren't awesome to deal with.

[rvagg]

finally landed in nodejs main nodejs/node#50650, should be in the next current release