-
Notifications
You must be signed in to change notification settings - Fork 42
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
Update workers/ from monorail results #800
Conversation
See #798 for the methodology
efdedf6
to
fc0582c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These initial results aren't super promising. Maybe it would make sense to get the titles of all bugs and eliminate ones which are clearly umbrella bugs?
workers/META.yml
Outdated
results: | ||
- test: dedicated-worker-parse-error-failure.html | ||
- product: chrome | ||
url: https://crbug.com/906850 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This bug doesn't link to opaque-origin.html but rather a sandboxed-iframe-with-opaque-origin.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, it does get returned from monorail search (https://bugs.chromium.org/p/chromium/issues/list?q=%2Fworkers%2Fopaque-origin.html&can=2)... I wonder if monorail splits on /
and I should be quoting these search terms -_-.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverted
See #798 for
the methodology