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
Fix some issues building on Windows #63
Conversation
- build.gradle: enforce UTF-8 as source code encoding - BotRunnerConfigurationTests.java: make assertion file separator agnostic - ProcessTests.java: disable test class on Windows, all tests call tools that are not present by default on Windows
Hi sormuras, welcome to this OpenJDK project and thanks for contributing! We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user sormuras as summary for the issue. If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing |
Thanks @sormuras for contributing! I know @JornVernee has been doing some work on getting the tests to pass on Windows as well, thank you for helping out in this area (me and @rwestberg use Linux and macOS). |
@sormuras This change can now be integrated. The commit message will be:
Since the source branch of this PR was last updated there have been 4 commits pushed to the
Since there are no conflicts, your changes will automatically be rebased on top of the above commits when integrating. If you prefer to do this manually, please merge As you do not have Committer status in this project, an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@edvbld) but any other Committer may sponsor as well.
|
@sormuras I'm guessing you're also on HG version 5? I'm seeing the same failure on your last point, due to HG changing the internal API, and one of the extensions no longer working. |
That's correct:
I may downgrade to ... |
@sormuras I think Jorn already has a patch to get it working with 5.0.2, just hold on a little longer, no need to downgrade |
I also took the patch for a spin on my Linux x86_64 machine, all tests pass with |
off-topic Locally, I managed to upgrade Skara to JUnit |
@sormuras as the |
/integrate |
/sponsor |
Updated my fork and gave it a spin. Tests are now all(? still in progress...) running on Windows. |
Building skara on Windows requires at least following changes:
build.gradle
: enforce UTF-8 as source code encodingBotRunnerConfigurationTests.java
: make assertion file separator agnosticProcessTests.java
: disable test class on Windows, all tests call tools that are not present by default on WindowsAfter applying those changes, there're two more issues with building on Windows:
VersionPlugin.java
: there's anIOException
raised, which I handled by setting the version property to"unknown"
, around line 55:VCS.HG
, e.g.JCheckTests#checksForCommit(VCS.HG)
, fail with:java.io.UncheckedIOException: java.io.IOException: Num headers (1) differ from num hunks (0)
which might(!) be related to a) howgit.exe
/hg.exe
are invoked and/or b) due toUnixStreamReader
only interpreting\n
as a new line character ... or c) something completely different.Progress
Approvers