Closed
Bug 649690
Opened 14 years ago
Closed 13 years ago
Tegra Debug build reftests, crashtests
Categories
(Release Engineering :: General, defect, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: martijn.martijn, Assigned: mozilla)
References
Details
(Whiteboard: [mobile][unittest][tegra][mobile_unitttests][android_tier_1])
Attachments
(1 file, 1 obsolete file)
7.76 KB,
patch
|
bear
:
review+
mozilla
:
checked-in+
|
Details | Diff | Splinter Review |
From bug 643607, comment 18 and 19:
"
It was mentioned on the meeting today (
https://wiki.mozilla.org/Mobile/Notes/13-Apr-2011#Test_Automation ), that the
JS team would like to have debug builds tested on the tegra boards, testing js
tests/js reftests.
Mfinkle mentioned that you should be able to get to the logcat output , because
there is no other way to get the stdout.
Perhaps a new bug be filed for this, Aki?
"
Aki:
"
We have bug 581290 for debug builds.
And sure, we need a bug for debug build tests.
"
Assignee | ||
Updated•14 years ago
|
Summary: Debug build tests for js → Tegra Debug build reftests, crashtests
Whiteboard: [mobile][unittest][tegra]
Assignee | ||
Comment 1•14 years ago
|
||
[11:13] <bmoss> ok, so assuming the run doesn't cause the log file to rotate we could do an 'exec su -c "logcat -d" ' and put that output into a file
[11:14] <aki> after the test run?
[11:14] <bmoss> kinda like calling cat
[11:14] <bmoss> yes after the run
Assignee | ||
Comment 2•14 years ago
|
||
Updated•14 years ago
|
Priority: -- → P4
Updated•14 years ago
|
Whiteboard: [mobile][unittest][tegra] → [mobile][unittest][tegra][mobile_unitttests]
Updated•13 years ago
|
Whiteboard: [mobile][unittest][tegra][mobile_unitttests] → [mobile][unittest][tegra][mobile_unitttests][android_tier_1]
Updated•13 years ago
|
Assignee: nobody → aki
Assignee | ||
Comment 3•13 years ago
|
||
I need to investigate the logcat + do some testing.
But this passes test_masters and I see the debug test builders in dump_masters.
Assignee | ||
Comment 4•13 years ago
|
||
I'm running these tests now.
* They're running!
* Crashtests have 29 test fails (1893/29/45) so orange.
* Reftests are still running in staging.
Would it help to enable these without having the full logcat, or are they useless without that?
Asking because we can enable them very soon, or we can leave 'em off until we have more ability to get stdout. Not sure how long that will take but I suspect it won't be perfect in the near future.
Assignee | ||
Comment 5•13 years ago
|
||
Per the mobile meeting,
* running these without logcat will be useful, so turn them on now
* m-c only til they're no longer perma-orange.
I will rescope the patch for review.
Assignee | ||
Comment 6•13 years ago
|
||
This makes enable_opt_unittests true by default and cleans up some related cruft.
(have to turn it back off on devtools to pass test-masters.)
It also adds the debug unittests, off by default, and enables them on Try and m-c.
Attachment #553982 -
Attachment is obsolete: true
Attachment #555558 -
Flags: review?(bear)
Updated•13 years ago
|
Attachment #555558 -
Flags: review?(bear) → review+
Assignee | ||
Comment 7•13 years ago
|
||
Comment on attachment 555558 [details] [diff] [review]
android debug tests for m-c and try
http://hg.mozilla.org/build/buildbot-configs/rev/2c7565040114
Attachment #555558 -
Flags: checked-in+
Assignee | ||
Updated•13 years ago
|
Flags: needs-reconfig?
Assignee | ||
Comment 8•13 years ago
|
||
These are now on in m-c and Try.
I'll file a followup bug to add logcat to debug tegra unittests, but this isn't an easy ask so may take a while.
Once these tests are no longer perma-orange, we can enable them on all branches.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•13 years ago
|
Flags: needs-reconfig?
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•