Enable all Angular Bazel Tests on Windows #29785
Milestone
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 |
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 25, 2019
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
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 25, 2019
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
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 25, 2019
Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 25, 2019
Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 25, 2019
This PR parially addresses angular#29785 and fixes ` //packages/language-service/test:test`
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 25, 2019
This PR parially addresses angular#29785 and fixes ` //packages/language-service/test:test`
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 26, 2019
Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 26, 2019
Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 26, 2019
This fixes the below test target in Windows ``` //packages/compiler/test:test ``` Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 26, 2019
This fixes the below test target in Windows ``` //packages/compiler/test:test ``` Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 26, 2019
This fixes the below test target in Windows ``` //packages/compiler/test:test ``` Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 26, 2019
This fixes the below test target in Windows ``` //packages/compiler/test:test ``` Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 26, 2019
``` //packages/compiler-cli/test:ngc //packages/compiler/test:test ``` This also address `node_modules` to the ignored paths for ngcc compiler as otherwise the `ready` is never fired Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
Apr 26, 2019
``` //packages/compiler-cli/test:ngc //packages/compiler/test:test ``` This also address `node_modules` to the ignored paths for ngcc compiler as otherwise the `ready` is never fired Partially addresses angular#29785
kara
added a commit
that referenced
this issue
May 7, 2019
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
May 7, 2019
``` //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
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
May 7, 2019
``` //packages/compiler-cli/ngcc/test:test ``` Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
May 7, 2019
``` //packages/compiler-cli/ngcc/test:integration ``` Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
May 9, 2019
Under Windows, the server binrary has an extenstion of `.exe` and the current logic is not handling that. Partially addresses: angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
May 9, 2019
Under Windows, the server binrary has an extenstion of `.exe` and the current logic is not handling that. Partially addresses: angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
May 9, 2019
Under Windows, the server binary has an extension of `.exe` and the current logic is not handling that. Partially addresses: angular#29785
alxhub
added a commit
that referenced
this issue
May 9, 2019
alxhub
added a commit
that referenced
this issue
May 9, 2019
Closed
alxhub
added a commit
that referenced
this issue
May 13, 2019
alxhub
added a commit
that referenced
this issue
May 13, 2019
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
May 13, 2019
``` //packages/compiler-cli/ngcc/test:test ``` Partially addresses angular#29785
alan-agius4
added a commit
to alan-agius4/angular
that referenced
this issue
May 13, 2019
``` //packages/compiler-cli/ngcc/test:integration ``` Partially addresses angular#29785
alxhub
added a commit
that referenced
this issue
May 13, 2019
alxhub
added a commit
that referenced
this issue
May 13, 2019
BioPhoton
added a commit
to BioPhoton/angular
that referenced
this issue
May 21, 2019
鈥�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
BioPhoton
added a commit
to BioPhoton/angular
that referenced
this issue
May 21, 2019
This PR parially addresses angular#29785 and fixes ` //packages/language-service/test:test` PR Close angular#30113
BioPhoton
added a commit
to BioPhoton/angular
that referenced
this issue
May 21, 2019
Partially addresses angular#29785 PR Close angular#30111
BioPhoton
added a commit
to BioPhoton/angular
that referenced
this issue
May 21, 2019
``` //packages/compiler-cli/integrationtest:integrationtest //packages/compiler-cli/test/compliance:compliance ``` Partially addresses angular#29785 PR Close angular#30189
BioPhoton
added a commit
to BioPhoton/angular
that referenced
this issue
May 21, 2019
鈥�#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
BioPhoton
added a commit
to BioPhoton/angular
that referenced
this issue
May 21, 2019
``` //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
BioPhoton
added a commit
to BioPhoton/angular
that referenced
this issue
May 21, 2019
``` //packages/compiler-cli/ngcc/test:test ``` Partially addresses angular#29785 PR Close angular#30297
BioPhoton
added a commit
to BioPhoton/angular
that referenced
this issue
May 21, 2019
``` //packages/compiler-cli/ngcc/test:integration ``` Partially addresses angular#29785 PR Close angular#30297
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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-onlywith 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.exeis 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-onlyivy-onlyCurrent TODO list is:
bazel-0.24.1 build --nobuild //... --incompatible_bzl_disallow_load_after_statementNote that we still need
--incompatible_bzl_disallow_load_after_statement=falseuntil the incompatibility issue is fixed.If you failed to build brotli, you can use the following in
packages/bazel/package.bzl: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: