Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Path name too long" errors in JDK11/hotspot/windows builds #1646

Closed
sxa opened this issue Apr 2, 2020 · 3 comments · Fixed by #1647
Closed

"Path name too long" errors in JDK11/hotspot/windows builds #1646

sxa opened this issue Apr 2, 2020 · 3 comments · Fixed by #1647
Assignees
Labels
bug Issues that are problems in the code as reported by the community
Milestone

Comments

@sxa
Copy link
Member

sxa commented Apr 2, 2020

Potentially introduced by #1639

Ref: https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-windows-x86-32-hotspot/464/console / https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-windows-x86-32-hotspot/464/console

c1 : fatal error C1081: 'c:/cygwin64/tmp/openjdk-build/jdk11u-windows-x86-32-hotspot/workspace/build/src/build/windows-x86-normal-clientANDserver-release/support/test/hotspot/jtreg/native/support/libGetOwnedMonitorStackDepthInfoWithEATest/libGetOwnedMonitorStackDepthInfoWithEATest.obj': file name too long
`

@sxa sxa added the bug Issues that are problems in the code as reported by the community label Apr 2, 2020
@sxa sxa assigned gdams Apr 2, 2020
@gdams
Copy link
Member

gdams commented Apr 2, 2020

@johnoliver looks like we'll need to make it even shorter....

@gdams
Copy link
Member

gdams commented Apr 2, 2020

for reference the current tmp drive is c:/cygwin64/tmp/openjdk-build/jdk11u-windows-x86-32-hotspot

@gdams
Copy link
Member

gdams commented Apr 2, 2020

in the previous setup we used /tmp/openjdk-jdk11u-windows-x86-32-hotspot

@gdams gdams linked a pull request Apr 2, 2020 that will close this issue
@karianna karianna added this to the April 2020 milestone Apr 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issues that are problems in the code as reported by the community
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants