Skip to content

Conversation

comius
Copy link
Contributor

@comius comius commented Nov 21, 2024

The CI setups claiming to run in WORKSPACE mode were wrong. This fixes it.

Disable integration tests on Windows WORKSPACE mode. They are failing: https://buildkite.com/bazel/rules-python-python/builds/9791#01934eac-3a03-445d-ad53-6683371ca289
Example failure: java.lang.UnsatisfiedLinkError: 'int com.google.devtools.build.lib.windows.WindowsFileOperations.nativeIsSymlinkOrJunction(java.lang.String, boolean[], java.lang.String[])'

@rickeylev rickeylev changed the title fix: flags on CI workspace setups tests: make workspace CI jobs enable workspace mode Nov 21, 2024
@rickeylev
Copy link
Collaborator

Oh dang, thanks for noticing that!

I pushed a fix for the integration test failure. Looked like just a difference in case on windows. Also changed the windows CI to not skip the integration tests.

@rickeylev rickeylev enabled auto-merge November 21, 2024 19:03
@rickeylev
Copy link
Collaborator

I spoke too soon. Most of the //test/integration tests are failing with Windows+workspace with, yeah, that weird JNI linking error. I switched it back to skipping them again, for now.

@rickeylev rickeylev added this pull request to the merge queue Nov 21, 2024
Merged via the queue into bazel-contrib:main with commit d73a74f Nov 21, 2024
4 checks passed
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.

2 participants