-
Notifications
You must be signed in to change notification settings - Fork 25.9k
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
ci: cleanup ivy bazel tags #26735
ci: cleanup ivy bazel tags #26735
Conversation
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
A Googler has manually verified that the CLAs look good. (Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.) |
You can preview 640f655 at https://pr26735-640f655.ngbuilds.io/. |
So there's good news and bad news. 👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there. 😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request. Note to project maintainer: This is a terminal state, meaning the |
You can preview f5d353f at https://pr26735-f5d353f.ngbuilds.io/. |
You can preview d7901b1 at https://pr26735-d7901b1.ngbuilds.io/. |
9c0db65
to
4f0f6d0
Compare
You can preview 4f0f6d0 at https://pr26735-4f0f6d0.ngbuilds.io/. |
0e9e707
to
4c44d98
Compare
You can preview 4c44d98 at https://pr26735-4c44d98.ngbuilds.io/. |
You can preview 18dbd96 at https://pr26735-18dbd96.ngbuilds.io/. |
34eae68
to
1846935
Compare
You can preview 3d0c749 at https://pr26735-3d0c749.ngbuilds.io/. |
You can preview 1846935 at https://pr26735-1846935.ngbuilds.io/. |
You can preview aa2e09c at https://pr26735-aa2e09c.ngbuilds.io/. |
You can preview 318ba67 at https://pr26735-318ba67.ngbuilds.io/. |
With bazel-contrib/rules_nodejs#388 fixed we can stop messing around with tags and just rely on the explicitly defined tags. PR Close angular#26735
These tests were previously not running on CI so they have always been broken, or got broken just recently :-(. test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags PR Close angular#26735
…ntal variable (angular#26735) PR Close angular#26735
This means that we use the same command to run test on CI as when developing locally. PR Close angular#26735
…ivy-* tags (angular#26735) This target fails with odd error that we need to investigate: [01:19:32] I/direct - Using ChromeDriver directly... [01:19:32] E/direct - Error code: 135 [01:19:32] E/direct - Error message: Could not find chromedriver at /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/external/ngdeps/node_modules/webdriver-manager/selenium/chromedriver_2.41. Run 'webdriver-manager update' to download binaries. [01:19:32] E/direct - Error: Could not find chromedriver at /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/external/ngdeps/node_modules/webdriver-manager/selenium/chromedriver_2.41. Run 'webdriver-manager update' to download binaries. PR Close angular#26735
so that they are more suitable for CI usage. PR Close angular#26735
…6788) With bazel-contrib/rules_nodejs#388 fixed we can stop messing around with tags and just rely on the explicitly defined tags. PR Close #26735 PR Close #26788
…ivy-* tags (#26735) (#26788) This target fails with odd error that we need to investigate: [01:19:32] I/direct - Using ChromeDriver directly... [01:19:32] E/direct - Error code: 135 [01:19:32] E/direct - Error message: Could not find chromedriver at /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/external/ngdeps/node_modules/webdriver-manager/selenium/chromedriver_2.41. Run 'webdriver-manager update' to download binaries. [01:19:32] E/direct - Error: Could not find chromedriver at /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/external/ngdeps/node_modules/webdriver-manager/selenium/chromedriver_2.41. Run 'webdriver-manager update' to download binaries. PR Close #26735 PR Close #26788
With bazel-contrib/rules_nodejs#388 fixed we can stop messing around with tags and just rely on the explicitly defined tags. PR Close angular#26735
These tests were previously not running on CI so they have always been broken, or got broken just recently :-(. test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags PR Close angular#26735
…ntal variable (angular#26735) PR Close angular#26735
This means that we use the same command to run test on CI as when developing locally. PR Close angular#26735
…ivy-* tags (angular#26735) This target fails with odd error that we need to investigate: [01:19:32] I/direct - Using ChromeDriver directly... [01:19:32] E/direct - Error code: 135 [01:19:32] E/direct - Error message: Could not find chromedriver at /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/external/ngdeps/node_modules/webdriver-manager/selenium/chromedriver_2.41. Run 'webdriver-manager update' to download binaries. [01:19:32] E/direct - Error: Could not find chromedriver at /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/external/ngdeps/node_modules/webdriver-manager/selenium/chromedriver_2.41. Run 'webdriver-manager update' to download binaries. PR Close angular#26735
so that they are more suitable for CI usage. PR Close angular#26735
With bazel-contrib/rules_nodejs#388 fixed we can stop messing around with tags and just rely on the explicitly defined tags. PR Close angular#26735
These tests were previously not running on CI so they have always been broken, or got broken just recently :-(. test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags PR Close angular#26735
…ntal variable (angular#26735) PR Close angular#26735
This means that we use the same command to run test on CI as when developing locally. PR Close angular#26735
…ivy-* tags (angular#26735) This target fails with odd error that we need to investigate: [01:19:32] I/direct - Using ChromeDriver directly... [01:19:32] E/direct - Error code: 135 [01:19:32] E/direct - Error message: Could not find chromedriver at /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/external/ngdeps/node_modules/webdriver-manager/selenium/chromedriver_2.41. Run 'webdriver-manager update' to download binaries. [01:19:32] E/direct - Error: Could not find chromedriver at /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/external/ngdeps/node_modules/webdriver-manager/selenium/chromedriver_2.41. Run 'webdriver-manager update' to download binaries. PR Close angular#26735
so that they are more suitable for CI usage. PR Close angular#26735
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
we no longer need to rewrite the tags on the fly and can now rely on blacklisting via explicit tags set on individual targets.
this change revealed that we were not running certain tests on CI which have always been broken or got broken just recently. especially the hello world symbol test fix is concerning because it highlights a size regression that we need to investigate.