-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Add Logging and Debugging to Investigate RBE Failures #15409
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
Conversation
CI Feedback 🧐(Feedback updated until commit 846ba74)A test triggered by this PR failed. Here is an AI-generated analysis of the failure:
|
846ba74 to
d04f484
Compare
|
I fixed the things that need to get fixed for next release, I'll do a clean PR with the logging and debugging code later |
I thought most of the failures we have in trunk are related to CDP/browser/driver version mismatches, but that doesn't appear to be trueThis is WIP trying to make changes to get tests passing before release. Making it a PR for visibility and so it is easier to track.I've merged CDP and browser updates to trunk, but there are still failures.
This PR is now focused on getting more information about the RBE results so I can better figure out how to address the Ruby failures.