You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
+1 I suffered a lot in the last release that I made. So now, I need to think more how to fit the release work and all the retries in the schedule. I think that is a common feeling in the release team.
The lastest reliability report shows that most of the flakes come from unexpected errors in child process tests and timeouts in fs watch so there could be real bugs that need to be fixed. nodejs/reliability#789
Agreed, I've been trying to land #51645 for days and cannot get a green CI run. I don't have the time at the moment to fix some of these test mainly because it occurs on an OS I don't have access to like Windows or Linux Containered
Activity
UlisesGascon commentedon Feb 21, 2024
+1 I suffered a lot in the last release that I made. So now, I need to think more how to fit the release work and all the retries in the schedule. I think that is a common feeling in the release team.
joyeecheung commentedon Feb 21, 2024
The lastest reliability report shows that most of the flakes come from unexpected errors in child process tests and timeouts in fs watch so there could be real bugs that need to be fixed. nodejs/reliability#789
Ethan-Arrowood commentedon Feb 22, 2024
Agreed, I've been trying to land #51645 for days and cannot get a green CI run. I don't have the time at the moment to fix some of these test mainly because it occurs on an OS I don't have access to like Windows or Linux Containered
targos commentedon Sep 12, 2025
This is still a problem but we have nodejs/TSC#1614 now to track it.