Closed
Bug 860817
Opened 12 years ago
Closed 12 years ago
ensure we pull minidumps from android to the correct location on the host machine
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla23
People
(Reporter: jmaher, Assigned: jmaher)
Details
Attachments
(1 file)
1.23 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
it appears we are pulling the /mnt/sdcard/tests/profile/minidump/ directory into a tmp directory:
http://mxr.mozilla.org/mozilla-central/source/build/mobile/remoteautomation.py#126
Then we pass that tmp directory into automation.checkForCrashes:
http://mxr.mozilla.org/mozilla-central/source/build/automation.py.in#1165
the problem is in automation.py.in, we append 'minidumps' to the profile directory, so in this case checkForCrashes finds nothing.
Assignee | ||
Comment 1•12 years ago
|
||
this problem affect reftest and mochitest, not talos or xpcshell.
Assignee | ||
Comment 2•12 years ago
|
||
two solutions I can think of:
1) create dumpdir/minidumps, and use that to store the files in, then pass dumpdir to checkForCrashes
2) call mozcrash directly from runtestsremote.py passing in the proper directory to check for.
I prefer #1 although it appears as a much greater hack right now. If we change our code around checking for crashes outside of mozcrash, we will be able to address it for both desktop and mobile. Likewise we have self.test_last_seen.
#2 seems a lot cleaner.
opinions?
Comment 3•12 years ago
|
||
Well, right, automation.checkForCrashes takes a "profileDir" argument, and mozcrash just expects "the directory containing minidumps".
Comment 4•12 years ago
|
||
You could just make automation.checkForCrashes forward directly to mozcrash.check_for_crashes, and have the non-remote case append the "minidumps" to the profile dir.
Assignee | ||
Comment 5•12 years ago
|
||
thanks for option #3 ted, this is a simple patch. Up on try server, hoping for a crash or two.
Updated•12 years ago
|
Attachment #736718 -
Flags: review?(ted) → review+
Comment 6•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
You need to log in
before you can comment on or make changes to this bug.
Description
•