WebKit build can fail on Windows Server 2016 if path to repo is too long

Spotted in a test build on one of our Windows Server 2016 systems:

Can't stat C:/ADE/workspac/kcrjfx/label/win-2016-x64/jfx/rt/modules/javafx.web/src/main/native/Source/WebCore/Modules/gamepad: No such file or directory
 at C:/ADE/workspace/kcrjfx/label/win-2016-x64/jfx/rt/modules/javafx.web/src/main/native/Source/WebCore/bindings/scripts/generate-bindings-all.pl line 193.

Note that the path in question that cannot be opened has "workspac" rather than "workspace" in the name (you can see the correct path in the second line that points to the script that got the error).

The above was a non-fatal error, but eventually, we got this (where "win-016-x64" was used instead of "win-2016-x64") :

Can't stat C:/ADE/workspace/kcrjfx/label/win-016-x64/jfx/rt/modules/javafx.web/build/win/Release/WebCore/DerivedSources: No such file or directory
 at C:/ADE/workspace/kcrjfx/label/win-2016-x64/jfx/rt/modules/javafx.web/src/main/native/Source/WebCore/bindings/scripts/generate-bindings-all.pl line 193.
[1/13] GCObservation.idl
[2/13] InternalSettings.idl
[3/13] Internals.idl
[4/13] InternalsMapLike.idl
[5/13] InternalsSetLike.idl
[6/13] MallocStatistics.idl
[7/13] MemoryInfo.idl
[8/13] MockCDMFactory.idl
[9/13] MockContentFilterSettings.idl
[10/13] MockPageOverlay.idl
[11/13] ServiceWorkerInternals.idl
[12/13] TypeConversions.idl
[13/13] InternalSettingsGenerated.idl
Could NOT find IDL file for interface "InternalSettingsGenerated", reachable from "InternalSettings"!
$VAR1 = ' at /cygdrive/c/ADE/workspace/kcrjfx/label/win-2016-x64/jfx/rt/modules/javafx.web/src/main/native/Source/WebCore/bindings/scripts/CodeGenerator.pm line 614.
CodeGenerator::ParseInterface(CodeGenerator=HASH(0x801126140), IDLInterface=HASH(0x801125f48), "InternalSettingsGenerated") called at /cygdrive/c/ADE/workspace/kcrjfx/label/win-2016-x64/jfx/rt/modules/javafx.web/src/main/native/Source/WebCore/bindings/scripts/CodeGenerator.pm line 545

An identical job with a shorter path name to the repo passed (although there were still some non-fatal errors). Oddly enough an identical job with a slightly longer path name to the repo also passed (again, with non-fatal error).

This does not happen on Windows 11.