Skip to content

CI: expand %ProgramFiles% manually #29716

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

Merged
merged 1 commit into from
Feb 8, 2020

Conversation

compnerd
Copy link
Member

@compnerd compnerd commented Feb 8, 2020

This expands %ProgramFiles% manually since it is getting expanded to
C:\Program Files (x86) rather than C:\Program Files as expected.
Although this is less portable, this will at least enable the CI to run
properly.

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

This expands `%ProgramFiles%` manually since it is getting expanded to
`C:\Program Files (x86)` rather than `C:\Program Files` as expected.
Although this is less portable, this will at least enable the CI to run
properly.
@compnerd
Copy link
Member Author

compnerd commented Feb 8, 2020

CC: @drodriguez

@compnerd
Copy link
Member Author

compnerd commented Feb 8, 2020

@swift-ci please test Windows platform

Copy link
Contributor

@drodriguez drodriguez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good that you noticed, because I looked at the logs and I wasn't able to see the problem. W.T.F.

@compnerd
Copy link
Member Author

compnerd commented Feb 8, 2020

The reason that we couldn't figure it out is that the Java process is 32-bit which means that %ProgramFiles% is actually %ProgramFiles(x86)% and %ProgramFiles(x86)% is NaT. The result is that the wrong executable path was being used. Of course I couldn't see that without the verbose mode. I think that we should just leave the verbose mode enabled.

@drodriguez
Copy link
Contributor

Why are you not using Java 64 bits? No problem using the 32 bits one, but is it an intentional choice?

Also, no problem leaving the echo on.

@swift-ci please smoke test and merge

@swift-ci swift-ci merged commit 6de9f11 into swiftlang:master Feb 8, 2020
@compnerd compnerd deleted the correctness-over-portability branch February 8, 2020 17:06
@compnerd
Copy link
Member Author

compnerd commented Feb 8, 2020

I couldn't find the 64-bit Java from their website without having to register. I just didn't want the hassle of the registration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants