build: share Saucelabs browsers between karma test targets using background Saucelabs daemon and custom karma launcher#49200
Conversation
c7041de to
eb4438a
Compare
eb4438a to
0ffd098
Compare
0ffd098 to
dfeb669
Compare
dfeb669 to
a954864
Compare
d7ce225 to
3c4aca3
Compare
e90f275 to
d61891f
Compare
bb51091 to
8b4672a
Compare
devversion
left a comment
There was a problem hiding this comment.
Overall LGTM- but I'm definitely biased a bit 😄
Next steps would be:
- Addressing the feedback & landing this
- Making sure all parts are tested, like with the legacy job
- Replace the legacy job & delete code, in favor of just the Bazel job
JiaLiPassion
left a comment
There was a problem hiding this comment.
LGTM!
Reviewed-for: fw-zones
dgp1130
left a comment
There was a problem hiding this comment.
Reviewed-for: code-ownership
I'll defer to others on the actual implementation, but I can at least LGTM the PullApprove change.
devversion
left a comment
There was a problem hiding this comment.
LGTM. Couple of more comments, but close. Can you please push feedback as fixup commits?
5985f04 to
283f782
Compare
9c601fe to
e687ce2
Compare
Ready for another pass @devversion. Changes since last review: e687ce2 |
e687ce2 to
0cdcaec
Compare
devversion
left a comment
There was a problem hiding this comment.
LGTM. final comments. thanks Greg!
…ground Saucelabs daemon and custom karma launcher This upgrades the Saucelabs Bazel step on CI to use the more efficient Saucelabs daemon
abcf220 to
4954589
Compare
…s.sh script for local testing more chars to meet the linters requirements
…onal chars to meet commit msg formatting requirements plus more additional chars here
4954589 to
29891e9
Compare
|
Last CI run with saucelabs tests enabled on PRs with passing tests: https://app.circleci.com/pipelines/github/angular/angular/60980/workflows/049e20fc-1957-45c2-b21c-4b0908577ee5/jobs/1335782 Removing the job from this PR now for landing as enabling it will be in a follow-up |
…followup additional test to make linter happy
| # Start the saucelabs-daemon background service in the background. Run directly from the generated | ||
| # bash script instead of using bazel run so we get the PID of the node process. Otherwise killing | ||
| # the child process in kill_background_service doesn't kill the spawn node process. | ||
| cd dist/bin/tools/saucelabs-daemon/background-service/background-service.sh.runfiles/angular |
There was a problem hiding this comment.
I'm good with the code as is, but it seems a little unexpected to me. the Node process should be a child of the bazel run process, so it should be killed.
There was a problem hiding this comment.
It was surprising to me as well. Could use some more investigation in the future.
There was a problem hiding this comment.
this is just the convenience script anyway right?
There was a problem hiding this comment.
yes, this is not used on CI at all
devversion
left a comment
There was a problem hiding this comment.
LGTM
Reviewed-for: global-dev-infra-approvers
|
This PR was merged into the repository by commit d0262cd. |
|
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. |
Picks up the work that @devversion started in the components repo.
Plan is to move this to the dev tools in a follow-up.