-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Reduce non-highmem browser testing #23911
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
This reduces the number of tests run in the "default" browser test modes (i.e. non-2g 32bit and non-4g 64-bit). The idea is that the set of edge cases covered by the 2g and 4g modes is basically a superset of those covered by the default cases. Tests that are disabled in the 2g and 4g modes are still run in the default modes.
This does still keep some tests running in the default modes, just to make sure that no tests are skipped entirely. |
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.
LGTM with comments and maybe TODO to restore some day?
test_2gb_fail, test_4gb_fail and test_2gb are failing here in test-browser-chrome-wasm64. Were they working before? |
oh nevermind, they were skipped before. |
The 4gb_fail test looks like it was deliberately skipped (your removed that line). |
This reduces the number of tests run in the "default" browser test modes
(i.e. non-2g 32bit and non-4g 64-bit). The idea is that the set of edge
cases covered by the 2g and 4g modes is basically a superset of those
covered by the default cases. Tests that are disabled in the 2g and 4g
modes are still run in the default modes.