Closed Bug 861176 Opened 12 years ago Closed 11 years ago

Intermittent cppunittests TEST-UNEXPECTED-FAIL | TestSTSParser.exe | test failed with return code 4294967295 | Couldn't get the profile directory.

Categories

(Release Engineering :: General, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Assigned: dougt)

References

Details

(Keywords: intermittent-failure)

Interestingly, we hit this first on mozilla-release a few days ago, hadn't seen it since, and then hit it on inbound. https://tbpl.mozilla.org/php/getParsedLog.php?id=21720569&tree=Mozilla-Inbound WINNT 5.2 mozilla-inbound build on 2013-04-11 13:27:24 PDT for push 13c33b6d787d slave: w64-ix-slave83 cppunittests INFO | Running test TestSTSParser.exe cppunittests TEST-UNEXPECTED-FAIL | TestSTSParser.exe | test failed with return code 4294967295 cppunittests INFO | Running test TestUDPServerSocket.exe Running STS Parser Tests tests... TEST-UNEXPECTED-FAIL | Couldn't get the profile directory. Finished running STS Parser Tests tests.
When someone starts looking for what happened between comment 4 and comment 5 to make this absolutely explode, what happened was that bug 852429 disabled running TestSettingsAPI, which had been taking the hit on these slaves with a tmpdir that can't create another file.
Depends on: 862355
Summary: Intemittent cppunittests TEST-UNEXPECTED-FAIL | TestSTSParser.exe | test failed with return code 4294967295 | Couldn't get the profile directory. → Intermittent cppunittests TEST-UNEXPECTED-FAIL | TestSTSParser.exe | test failed with return code 4294967295 | Couldn't get the profile directory.
Component: Networking → Release Engineering: Automation (General)
Product: Core → mozilla.org
QA Contact: catlee
Version: Trunk → other
Doug, can you find an appropriate owner for this intermittent failure bug, this one's a pretty high frequency failure one...
Assignee: nobody → doug.turner
jst: I think we're waiting on bug 862355 to get fixed since it may have caused this one. It also seems to have triggered bug 852429. Gregor disabled the failing test there, since 862355 wasn't moving (https://bugzilla.mozilla.org/show_bug.cgi?id=852429#c484). I don't think we should disable the STS parser compiled code tests, and bug 852429 got a review today so hopefully this will be fixed soon.
I think you might still have a profile-related bug besides the exploding one, but just the thought of looking for the failure that made me think so among those 400 others makes me tired. If it wants to be seen, it can happen again, fixed by bug 862355.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.