Disable default MAX_PATH length limit for Windows agents in RelEng JIPP
Summary
After the remoteFS of the native build agents was prepared for usage in multiple JIPPs via https://github.com/eclipse-cbi/jiro/pull/379, for #4231, we now see errors in I-build tests on Windows that indicate that the paths are too long:
https://github.com/eclipse-pde/eclipse.pde/issues/1333
The simplest solution (and hopefully one without other drawbacks) could be to disable the Maximum Path Length Limitation, that is enabled on Windows by default, for the Windows build agents in the RelEng JIPP:
-
https://ci.eclipse.org/releng/computer/qa6xd%2Dwin11/
This one currently executes the I-build tests for win-x86_64 so it should definitively be fixed -
https://ci.eclipse.org/releng/computer/rie8t%2Dwin11%2Darm64/
This one will hopefully soon execute I-build tests for win-arch -
https://ci.eclipse.org/releng/computer/rs68g%2Dwin10/
To be consistent with the other machines it would be good to disable the limit here too (if possible).
This article describes how this can be changed in the Windows Registry: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=powershell#enable-long-paths-in-windows-10-version-1607-and-later
Would that be feasible?
FYI @akurtakov and @aloskutov
Priority
- Urgent
- High
- Medium
- Low
Severity
- Blocker
- Major
- Normal
- Low
Activity
added IT-prioritymedium IT-severitynormal labels
assigned to @pstankie
added statewip label
added Servers team:releng labels
Thank you.
Unfortunately further investigation has revealed that this option has no effect when launching processes with long working directory paths. I have therefore created the following PR to implement a workaround in the Eclipse launching facility that should at least help a little bit (how much depends on the structure of the exact path): https://github.com/eclipse-platform/eclipse.platform/pull/1477
removed statewip label
mentioned in issue #5253 (closed)
