-
Notifications
You must be signed in to change notification settings - Fork 209
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
Fail on unexpected Javascript console errors #4288
Fail on unexpected Javascript console errors #4288
Conversation
d119af5
to
a2e4251
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.
I am not convinced to move the Test::More calls into the function as I learned that test failure feedback works best if the scope of such calls is the top-level test code and everything on a lower level should return the errors as boolean result
The advantage of this approach is that we cannot forget to actually use the return value but I also get @okurz 's point. It would be great if Perl had a |
a2e4251
to
292ee2a
Compare
No idea what this is:
|
chrome also crashed for me in #4289 |
292ee2a
to
79ab5cb
Compare
chrome problems worked around in #4291 , I had already approved. Approval still holds :) |
8f4cf0c
to
330ce21
Compare
330ce21
to
60b5048
Compare
968e0cb
to
3ca9299
Compare
Looks like the test failures are actually related.
Maybe this warning should be ignored?
|
This looks like the symptom of the json file never being written:
|
This is the one I'd added before but dropped when making all fatal. Which means I'm adding it back now. |
3ca9299
to
03d0721
Compare
Codecov Report
@@ Coverage Diff @@
## master #4288 +/- ##
==========================================
- Coverage 97.94% 97.94% -0.01%
==========================================
Files 371 371
Lines 33705 33704 -1
==========================================
- Hits 33012 33011 -1
Misses 693 693
Continue to review full report at Codecov.
|
This pull request is now in conflicts. Could you fix it? 🙏 |
4f54cec
to
b9f4af8
Compare
Whilst os-autoinst#4352 doesn't work I'm opening this to provide a reference for the stability of os-autoinst#4288.
Whilst os-autoinst#4352 doesn't work I'm opening this to provide a reference for the stability of os-autoinst#4288.
b9f4af8
to
95d4a25
Compare
Whilst os-autoinst#4352 doesn't work I'm opening this to provide a reference for the stability of os-autoinst#4288.
b16843b
to
39f790b
Compare
39f790b
to
f0f088e
Compare
34f85e8
to
2b9f274
Compare
The function merely returns a truthy value. Let's fail always without relying on the caller. This means we will see errors in all cases, not just when something else happens to fail. I'm also dropping a comment claiming the function aborts.
2b9f274
to
48664aa
Compare
commit eab2bad Merge: 4c2ce7a 48664aa Author: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> AuthorDate: Mon Nov 22 06:27:15 2021 +0000 Commit: GitHub <noreply@github.com> CommitDate: Mon Nov 22 06:27:15 2021 +0000 Merge pull request os-autoinst#4288 from kalikiana/full_stack_t_console_errors Fail on unexpected Javascript console errors
This fixes an error introduced with os-autoinst#4288 where an additional "if"-expression was introduced looking for two alternatives "javascript" or "network" for the error source which means that we never enter the next elsif-sections for such errors. This commit simply removes the distinction of javascript error sources as we can be strict enough with our individual regex's looking for specific errors to skip. Related progress issue: https://progress.opensuse.org/issues/102578
The function merely returns a truthy value. Let's fail always without relying on the caller. This means we will see errors in all cases, not just when something else happens to fail.
I'm also dropping a comment claiming the function aborts.
See: https://progress.opensuse.org/issues/98952