Closed Bug 689839 Opened 13 years ago Closed 13 years ago

Intermittent Android test failure with "INFO | automation.py | Application ran for: 0:18:nn.nnnnnn" (or 0:19 or 0:12 or 1:01) after repeated "DeviceManager: error pulling file: No such file or directory"

Categories

(Release Engineering :: General, defect, P3)

Product:
Release Engineering
Component:
General
Platform:
ARM
Android
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [mobile_unittests][android_tier_1])

+++ This bug was initially created as a clone of Bug #686091 +++ The ones I (perhaps mistakenly, perhaps correctly) put in bug 686091: https://tbpl.mozilla.org/php/getParsedLog.php?id=6573047&tree=Mozilla-Inbound https://tbpl.mozilla.org/php/getParsedLog.php?id=6571506&tree=Firefox The pattern is that runtests starts, then there's nothing but a repeated bunch of DeviceManager: error pulling file: No such file or directory DeviceManager: error pulling file: No such file or directory with maybe the odd bit of "reconnecting socket", until INFO | automation.py | Application ran for: 0:18:21.895556 INFO | automation.py | Reading PID log: /tmp/tmpL1DLo9pidlog WARNING | automationutils.processLeakLog() | refcount logging is off, so leaks can't be detected! INFO | runtests.py | Running tests: end. DeviceManager: error pulling file: No such file or directory removing file: /data/data/com.mozilla.SUTAgentAndroid/files/tests/logs/mochitest.log program finished with exit code 0 elapsedTime=1111.231595 TinderboxPrint: mochitest-browser-chrome<br/> so "18 minutes" (rather than the 18 seconds that made me think this was bug 686091 altered by some changes that added 3 seconds, though it certainly could be altered by some changes that added 18 minutes and change, who knows?), and no output other than failing to pull a file and maybe some socket reconnecting is what I'm claiming this set of symptoms of an unknown problem are. From bug 686091 comment 46: "This indicates that the test had some type of error while trying to run the tests, either a bad profile or something wrong with the build or tests. We would see other errors if the tegra was unreachable or offline."
https://tbpl.mozilla.org/php/getParsedLog.php?id=6575214&tree=Firefox https://tbpl.mozilla.org/php/getParsedLog.php?id=6584895&tree=Mozilla-Inbound Maybe that reconnecting socket just before the last error pulling file is An Clue, since the last three I looked at have all had it right there.
Summary: Intermittent Android test failure with "INFO | automation.py | Application ran for: 0:18:nn.nnnnnn" after repeated "DeviceManager: error pulling file: No such file or directory" → Intermittent Android test failure with "INFO | automation.py | Application ran for: 0:18:nn.nnnnnn" (or 0:19:nn.nnnnnn) after repeated "DeviceManager: error pulling file: No such file or directory"
https://tbpl.mozilla.org/php/getParsedLog.php?id=6590061&tree=Mozilla-Inbound - a 12 minute browser-chrome.
Summary: Intermittent Android test failure with "INFO | automation.py | Application ran for: 0:18:nn.nnnnnn" (or 0:19:nn.nnnnnn) after repeated "DeviceManager: error pulling file: No such file or directory" → Intermittent Android test failure with "INFO | automation.py | Application ran for: 0:18:nn.nnnnnn" (or 0:19 or 0:12) after repeated "DeviceManager: error pulling file: No such file or directory" with a single "reconnecting socket" before the last one
I just can't seem to get the summary right. https://tbpl.mozilla.org/php/getParsedLog.php?id=6590708&tree=Mozilla-Inbound is a M8 where all seven hunks ran for 1:01:2n, did nothing but find no file to pull, but did not try a socket reconnect just before giving up.
https://tbpl.mozilla.org/php/getParsedLog.php?id=6592968&tree=Mozilla-Inbound is a 19 minute M3, with a repeated reconnecting socket/unable to connect socket chunk. I probably had the right idea with the summary of bug 689856 :)
Priority: -- → P3
https://tbpl.mozilla.org/php/getParsedLog.php?id=6647705&tree=Firefox INFO | automation.py | Application ran for: 1:01:21.130573
https://tbpl.mozilla.org/php/getParsedLog.php?id=6677660&tree=Mozilla-Inbound I really should have gone with "It fails" for the summary.
Summary: Intermittent Android test failure with "INFO | automation.py | Application ran for: 0:18:nn.nnnnnn" (or 0:19 or 0:12) after repeated "DeviceManager: error pulling file: No such file or directory" with a single "reconnecting socket" before the last one → Intermittent Android test failure with "INFO | automation.py | Application ran for: 0:18:nn.nnnnnn" (or 0:19 or 0:12 or 1:01) after repeated "DeviceManager: error pulling file: No such file or directory"
I would have called https://tbpl.mozilla.org/php/getParsedLog.php?id=6768211&tree=Mozilla-Inbound this prior to automation.py starting to notice it was a crash; perhaps they all are.
this is fixed on trunk. Please reopen if you see it there. DO NOT REOPEN IF YOU SEE THIS ON RELEASE OR BETA (it will ride the trains)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [orange][mobile_unittests][android_tier_1] → [mobile_unittests][android_tier_1]
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.