build(bazel): run aio application e2e tests under bazel - #45952
Conversation
There was a problem hiding this comment.
Protractor depends on 12.1.7 but that version has a bug on m1 machines where the url to download the browser isn't correct.
57011e0 to
3ce818c
Compare
|
@devversion I added a second commit that uses the bazel-provided chromium toolchain. It's dependent on this fix for rules_nodejs: bazel-contrib/rules_nodejs#3456. I'll update and squash once that lands. |
There was a problem hiding this comment.
This is great! thanks. Out of curiosity, could we avoid the .. thing? this is actually a short-path already and likely you would need to resolve the path using the runfile helpers?
There was a problem hiding this comment.
The raw strings that these variables resolve to on my box are:
../org_chromium_chromedriver_linux_x64/chromedriver_linux64/chromedriver
../org_chromium_chromium_linux_x64/chrome-linux/chrome
They include a ../ which seems to already refer to a runfiles path? But they need a second ../ to counteract the chdir on this target.
Do you think I should still be using the runfile helpers?
There was a problem hiding this comment.
does this even work on windows? on windows the runfiles are not symlinked right?
There was a problem hiding this comment.
I tried to test this on my Windows vm but it looks like I've allowed a couple other things to regress on windows. I think I should start getting some of this running on ci, at least partially so I can check for any regressions on each PR. Are you okay with merging this as is and I'll do a Windows pass for the next PR?
82b6237 to
fe1d60e
Compare
There was a problem hiding this comment.
does this even work on windows? on windows the runfiles are not symlinked right?
Includes a postinstall fix for puppeteer so that chromium can be run with protractor on osx under bazel
|
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. |
@gkalpak @devversion @gregmagolan @josephperrott
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the new behavior?
The aio application e2e tests now run under bazel.
Does this PR introduce a breaking change?
Other information