Intermittent [ FAILED ] DatagramFragment13/TlsFragmentationAndRecoveryTest.DropFirstHalf/0, where GetParam() = true (1202 ms)
Categories
(NSS :: Libraries, defect, P3)
Tracking
(Not tracked)
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Filed by: jjones [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=266821836&repo=nss
Full log: https://queue.taskcluster.net/v1/task/DQDiNp6ARAWrCd4KJQ4--Q/runs/0/artifacts/public/logs/live_backing.log
Perma-failure starting from Bug 1579290
Comment 1•6 years ago
|
||
Marcus, can you poke at why this test is now failing?
Comment 2•6 years ago
|
||
I took a brief look and couldn't reproduce it. One place to start would be to add -v to the invocation of ssl_gtest so that we get more diagnostic output from these test runs.
Comment 3•6 years ago
•
|
||
I couldn't reproduce too, but generated some debug information to analyse and understand what happened. I will try to update here soon.
Comment 4•6 years ago
|
||
I tried a lot of ways to reproduce this problem:
- Change timeouts;
- Increase the fragments;
- Manipulate the handshaking;
- Increase the load of my local machine;
The only and closest way to reproduce this problem was manually braking the handshake in a way that one agent never send the last ACK.
At this point I was pretty sure that was a infrastructure problem.
Analysing these failed tasks and many other successful tasks with the same code, I could realize that the MAC instances looked very loaded during the failures, with high times to finish the gtests.
So, I crossed the performance of the tests in mac instances in a interval time before and after the Bug 1579290.
I couldn't find any relationship with the patch.
My conclusion was that these failures were caused by some infrastructure problem, related to high load of the mac instances.
Now, looks that this problem is not appearing anymore. We can leave this BUG open for some days or weeks to confirm that was a temporary problem. I will continue following...
Thanks
Comment hidden (Intermittent Failures Robot) |
Comment 6•6 years ago
|
||
Looks stable until now. Wait until next Tuesday to conclude.
Comment hidden (Intermittent Failures Robot) |
Comment 8•6 years ago
|
||
One more report 10 days after the first.
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2019-09-01&endday=2019-10-01&tree=all&bug=1581693
The second looks pretty similar the first. I continue believing that are external problems.
To be sure of that, some analysis in that specific instances are necessary.
I will continue following that.
Comment 9•6 years ago
|
||
Almost 20 days without the problem.
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2019-09-14&endday=2019-10-14&tree=all&bug=1581693
I am closing this BUG with WORKSFORME status as it couldn't be reproduced and no evidence was found suggesting something related to code BUGs.
Looks to be some temporary infrastructure problem.
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Comment hidden (Intermittent Failures Robot) |
Updated•5 years ago
|
Comment hidden (Intermittent Failures Robot) |
Updated•4 years ago
|
Comment 14•3 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Updated•3 years ago
|
Description
•