Closed Bug 973134 Opened 10 years ago Closed 8 years ago

Intermittent test_cert_overrides.js | Test timed out

Categories

(Core :: Security: PSM, defect, P3)

Product:
Core
Component:
Security: PSM
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: RyanVM, Unassigned)

References

(Depends on 1 open bug)

Details

https://tbpl.mozilla.org/php/getParsedLog.php?id=34700420&tree=Mozilla-Inbound

Ubuntu VM 12.04 mozilla-inbound opt test xpcshell on 2014-02-14 11:32:26 PST for push 4609a7efae47
slave: tst-linux32-ec2-006

11:59:35     INFO -  TEST-INFO | /builds/slave/test/build/tests/xpcshell/tests/security/manager/ssl/tests/unit/test_cert_overrides.js | running test ...
12:04:35  WARNING -  TEST-UNEXPECTED-FAIL | /builds/slave/test/build/tests/xpcshell/tests/security/manager/ssl/tests/unit/test_cert_overrides.js | Test timed out
12:21:15     INFO - Automation Error: mozprocess timed out after 1000 seconds running ['/builds/slave/test/build/venv/bin/python', '-u', '/builds/slave/test/build/tests/xpcshell/runxpcshelltests.py', '--symbols-path=https://ftp-ssl.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-linux/1392403133/firefox-30.0a1.en-US.linux-i686.crashreporter-symbols.zip', '--test-plugin-path=/builds/slave/test/build/application/firefox/plugins', '--manifest=tests/xpcshell/tests/all-test-dirs.list', '/builds/slave/test/build/application/firefox/xpcshell']
12:21:15    ERROR - timed out after 1000 seconds of no output
12:21:15    ERROR - Return code: -9
Assignee: nobody → dkeeler
Blocks: 967975
Component: Security → Security: PSM
David, I noticed this test takes a LONG time to run. I suspect it is doing some OCSP requests or something that might be doing I/O, unexpectedly.
I'm having trouble reproducing this locally. Having bug 804648 fixed would be helpful in that it might point me in the right direction.

Brian - I'm not seeing that this test takes a long time to run when successful. From my reading of the logs, it takes 3-4 seconds, which isn't that long compared to the other tests that use this infrastructure.
Depends on: 804648
(In reply to David Keeler (:keeler) from comment #12)
> Brian - I'm not seeing that this test takes a long time to run when
> successful. From my reading of the logs, it takes 3-4 seconds, which isn't
> that long compared to the other tests that use this infrastructure.

It was taking almost exactly 30 seconds when I ran it on my Windows 8.1 machine when I left my comment above. Other test take just a few seconds.

Just today, I actually reproduced the timeout, as the test took several minutes to complete. But, then I did a "mach build" and now the test is running in just a few seconds. If I reproduce any delays or hangs again I will let you know.

(Please use NEEDINFO?. I almost missed this comment.)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
OS: Linux → Gonk (Firefox OS)
Hardware: x86 → ARM
Resolution: WORKSFORME → ---
Looks like this either stopped happening or we don't care since b2g is tier 3. In any case, I'm unassigning myself. Let me know if there's anything further anyone needs me to do here.
Assignee: dkeeler → nobody
Mass whiteboard change to annotate PSM intermittent test failures as [psm-intermittent]. Filter on 31b932bd-1aad-4e29-9f4b-4cd864a3ffdc if that's important to you.
Whiteboard: [psm-intermittent]
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Yeah, we don't care whether or not b2g would still fail it if we ran it, but now that we are misstarring fresh obvious bustage of this test as though that were somehow sane, I don't want this bug to be open.
Status: REOPENED → RESOLVED
Closed: 9 years ago → 8 years ago
Keywords: intermittent-failure
Resolution: --- → INVALID
Whiteboard: [psm-intermittent]
You need to log in before you can comment on or make changes to this bug.