-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Windows, testing: make all tests work on Windows #4292
Comments
I'm tempted to make this bug P1. |
I'm, the most concerned about disabled
TBH with you: I stopped working on gerrit build on Windows, untill these tests are up and running. I was not amused to find out, that transitive classpath calculation in |
Strictly speaking, removing the warning from Bazel FAQ, that Windows support is bleeding edge, experimental and may produce unexpected results, was a mistake and this CL should be reverted. Nothing document this better as this issue. |
David, I'm not sure what reaction you expect. |
I'm seeing a problem that would likely be addressed by fixing these two tests:
Seems to occur when building multiple |
Split //src/test/j/c/g/d/b/lib:foundations_test into smaller tests, and enable many of them on Windows. Some tests are still tagged as "no_windows", either because they depend on ":unix", or because we need to fix them to pass on Windows. See #4292 Change-Id: Ibfab568a9e7b939c40f1301c9cfe06e60302755c PiperOrigin-RevId: 181936880
Add the j.c.g.d.build.android.desugar.runtime tests to the transitive closure of //src:all_windows_tests, thus running them on CI. See bazelbuild#4292
Add the j.c.g.d.build.android.desugar.runtime tests to the transitive closure of //src:all_windows_tests, thus running them on CI. See bazelbuild#4292
On Windows, enable some tests under c.g.d.build.android.desugar by adding them to the transitive closure of //src:all_windows_tests, thus running them on CI. See bazelbuild#4292 Change-Id: Ia2ff6e6b2bc83581d2d2ab2926d9ba40d44f96e2
Add the j.c.g.d.build.android.desugar.runtime tests to the transitive closure of //src:all_windows_tests, thus running them on CI. See bazelbuild#4292
I'm assuming this is why we have |
IIRC yes. Today we can skip incompatible targets (yay!) so filtering out incompatible tests is easier.
|
Standardizing internal/external BUILD file management. This does unfortunately remove tests from `all_windows_tests`, which seems like it's suffering from some bitrot (#4292 (comment)). We _could_ explicitly add the docgen tests, and while it's bound to be an unpopular opinion, I think we should avoid setting the precedent of explicitly enumerating windows tests as it's unlikely to scale. PiperOrigin-RevId: 379481390
WRT windows tests, copy pasting from another change... This does unfortunately remove tests from `all_windows_tests`, which seems like it's suffering from some bitrot (#4292 (comment)). We _could_ explicitly add the tests, and while it's bound to be an unpopular opinion, I think we should avoid setting the precedent of explicitly enumerating windows tests as it's unlikely to scale. PiperOrigin-RevId: 379819307
Since #3742 is no longer an issue on BuildKite (because we don't run bazel query first), I think we can switch to the |
Targets that should run on Windows but currently broken are listed in yml files and should be looked into, targets that don't run on Windows are marked as "no_windows". In total, 52 more tests are enabled on Windows. Related #4292 RELNOTES: None PiperOrigin-RevId: 380839138
After 572d4fd, we no longer rely on those targets to run Windows tests on Bazel CI. Related bazelbuild#4292
Ensures that the `build-info.properties` in deploy JARs has the same content across host operating systems. Along the way fixes a few other tests to get `//src/test/java/com/google/devtools/build/lib/rules/java/...` to pass on Windows. Work towards #4292 Closes #18073. PiperOrigin-RevId: 524864425 Change-Id: Iac5076788b92bd35d22e58d851447cee5a66fcc5
Ensures that the `build-info.properties` in deploy JARs has the same content across host operating systems. Along the way fixes a few other tests to get `//src/test/java/com/google/devtools/build/lib/rules/java/...` to pass on Windows. Work towards bazelbuild#4292 Closes bazelbuild#18073. PiperOrigin-RevId: 524864425 Change-Id: Iac5076788b92bd35d22e58d851447cee5a66fcc5
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team ( |
As of today, there are 282 tests that Bazel doesn't run on Windows.
EDIT(2017-12-13 15:52 +0100): we need to consider tests that check the current platform too, e.g. in Java do things like
OS.getCurrent() == OS.WINDOWS
.We need to make them all run on Windows and turn them on on CI, in order to have full test coverage on Windows.
The text was updated successfully, but these errors were encountered: