-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
test: Fix unintentional ignoring of console errors #19053
Conversation
This needs to be allowed. |
220dce5
to
a8c5bdf
Compare
We are left with:
|
49c3c5f
to
109c0fc
Compare
|
I'd suggest we let this run with just fedora-38/devel after a rebase and see what the damage is |
109c0fc
to
f903d9a
Compare
I rebased this and cleaned this up. See description for the aria stuff, let's handle that separately. Doing an initial run, and then I'll just add the aria bits to allowed messages. Then we have a nice laundry list of cleanups, and avoid introducing new ones. |
Ack, I agree with leaving the aria stuff for a later cleanup. |
f903d9a
to
c11160e
Compare
The first run is quite a mouthful. I went through with a coarse-grained |
I also changed the approach for fixing the |
debecdb
to
dedc93e
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.
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
Commit ccab549 broke the checking of browser errors, as with an unset `$TEST_ALLOW_JOURNAL_MESSAGES` (which is the case in our CI) it was adding the empty string as allowed pattern, which always matches. Ignore the React errors that happen with our current code, and add some explanations. We have so many of them that we can't fix all of them in one go, but we have to put a stop to introducing new ones. Some of them are test specific. Co-Authored-By: Martin Pitt <[email protected]>
dedc93e
to
56cbd6e
Compare
Argh, one more, due to a stupid typo. Fixed. It's blindingly obvious, so re-approving. |
Commit ccab549 broke the checking of browser errors, as with an
unset
$TEST_ALLOW_JOURNAL_MESSAGES
(which is the case in our CI) itwas adding the empty string as allowed pattern, which always matches.
Ignore the React errors that happen with our current code, and add some
explanations. We have so many of them that we can't fix all of them in
one go, but we have to put a stop to introducing new ones. Some of them
are test specific.
This PR originally had a lot of extra commits with aria updates. I split them out into PR #19496, but it's likely that they won't land, and we should ignore the aria warnings for the time being.