Stefan Stojanovic

> Is NtQueryInformationFile what fails, or the FileAllInformation query that fails? The function that fails is `NtQueryInformationFile` since it's the first one to get called (in order to get `NtQueryVolumeInformationFile`...

I understand. However, in this situation `fstat` solves the problem, plus it is only used if `NtQueryInformationFile` fails and only for the stdio streams, so it's a very limited usage....

A different solution to this problem (without the CRT) can be reviewed [here](https://github.com/libuv/libuv/pull/3811)

I deleted the v14 job and added the v18 and v20 ones. As suggested, I left the v16 job. I'll check the runs new jobs had over the weekend on...

The jobs are created and they are running daily. However, both have been red since starting, and failures are happening on various platforms. As I recall we've been marking some...

This issue seems no longer relevant as it has been stale for some time. If there are no objections, I will close this issue next Mon-Tue. In case something similar...

> @nodejs/build-infra Just curious; at least this PR and #48275 reports the exact same failures with Windows see [#48275 (comment)](https://github.com/nodejs/node/pull/48275#issuecomment-1581356301), is there any chance that infra is broken for the...

> /cc @nodejs/platform-windows @StefanStojanovic We're hitting [nodejs/node-v8#271](https://github.com/nodejs/node-v8/issues/271) Thanks for letting me know. I just got back to work today, so will look into it in the following days.

> Can we add a test so we don't regress? Of course. I'll add it next week.

> Can we add a test so we don't regress? Test's added.