-
Notifications
You must be signed in to change notification settings - Fork 26.2k
Enable all Angular Bazel Tests on Windows #29785
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
Comments
Tests to be fixed: --build_tag_filters=-ivy-only --test_tag_filters=-ivy-only:
--define=compile=aot --build_tag_filters=-no-ivy-aot,-fixme-ivy-aot --test_tag_filters=-no-ivy-aot,-fixme-ivy-aot
|
note, we can publish nightly snapshots of Bazel to npm, so we don't necessarily need to wait for fixes to be released. I started this in https://github.com/alexeagle/rules_nodejs/tree/nightly_bazel but need some help to finish probably |
This change addresses several issues with ts-api-guardian and public api guards related tests in Windows The fixes contain 3 main changes: 1) In `stripExportPattern` - replace `^` with `^^^^` in RegExp due to a double escaping requirment under Windows. Note that under Linux this the extra character has no effect because it's still a valid RegExp in Js. 2. Force `*.patch` files to always be with a LF line sequence instead of CRLF in windows 3. When adding JSDoc comments consider the presence of a carriage return in a line new feed Partially addresses #29785 PR Close #30105
This change addresses several issues with ts-api-guardian and public api guards related tests in Windows The fixes contain 3 main changes: 1) In `stripExportPattern` - replace `^` with `^^^^` in RegExp due to a double escaping requirment under Windows. Note that under Linux this the extra character has no effect because it's still a valid RegExp in Js. 2. Force `*.patch` files to always be with a LF line sequence instead of CRLF in windows 3. When adding JSDoc comments consider the presence of a carriage return in a line new feed Partially addresses #29785 PR Close #30105
#30252 will be fixed by bazelbuild/bazel@6e75219, which will be released with 0.26.0 I can help look into #30251, this looks like a bug instead of a real performance issue. |
…30105) This change addresses several issues with ts-api-guardian and public api guards related tests in Windows The fixes contain 3 main changes: 1) In `stripExportPattern` - replace `^` with `^^^^` in RegExp due to a double escaping requirment under Windows. Note that under Linux this the extra character has no effect because it's still a valid RegExp in Js. 2. Force `*.patch` files to always be with a LF line sequence instead of CRLF in windows 3. When adding JSDoc comments consider the presence of a carriage return in a line new feed Partially addresses angular#29785 PR Close angular#30105
This PR parially addresses angular#29785 and fixes ` //packages/language-service/test:test` PR Close angular#30113
Partially addresses angular#29785 PR Close angular#30111
``` //packages/compiler-cli/integrationtest:integrationtest //packages/compiler-cli/test/compliance:compliance ``` Partially addresses angular#29785 PR Close angular#30189
…#30346) Under Windows, the server binary has an extension of `.exe` and the current logic is not handling that. Partially addresses: angular#29785 PR Close angular#30346
``` //packages/compiler-cli/test:ngc //packages/compiler/test:test ``` This also address `node_modules` to the ignored paths for ngc compiler as otherwise the `ready` is never fired Partially addresses angular#29785 PR Close angular#30146
``` //packages/compiler-cli/ngcc/test:test ``` Partially addresses angular#29785 PR Close angular#30297
``` //packages/compiler-cli/ngcc/test:integration ``` Partially addresses angular#29785 PR Close angular#30297
🐞 bug report
Is this a regression?
Nope
Description
Angular tests are only partially enabled on Windows:
angular/.codefresh/codefresh.yml
Lines 22 to 24 in 1102b02
To have better Windows support, we should be able to run all tests on Windows, that is:
(IIUC,
yarn test-ivy-aot //...
is essentiallybazel test --define=compile=aot --build_tag_filters=-no-ivy-aot,-fixme-ivy-aot --test_tag_filters=-no-ivy-aot,-fixme-ivy-aot //...
)I tried to run all tests without
ivy-only
with Bazel 0.24.1 and gotSee full detail at Angular test with Bazel 0.24.1
It turned out all broken tests are because
powershell.exe
is not available when using--incompatible_strict_action_env
. So I sent a change in Bazel to fix this problem. bazelbuild/bazel@6e75219With Bazel@6e75219, after working around some incompatibility issues, I'm able to build and run all Angular tests on Windows. The results are:
ivy-only
ivy-only
Current TODO list is:
bazel-0.24.1 build --nobuild //... --incompatible_bzl_disallow_load_after_statement
🔬 Minimal Reproduction
Note that we still need
--incompatible_bzl_disallow_load_after_statement=false
until the incompatibility issue is fixed.If you failed to build brotli, you can use the following in
packages/bazel/package.bzl
:🌍 Your Environment
Angular Version:
@alexeagle @filipesilva Can you point this issue to correct people in Angular Windows team? I will also continue to help investigating.
The text was updated successfully, but these errors were encountered: