Closed
Bug 649975
Opened 14 years ago
Closed 14 years ago
No output for Tshutdown in Mobile Ts test
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mfinkle, Assigned: jmaher)
References
Details
(Whiteboard: [mobile_unittests])
Attachments
(1 file)
|
1.07 KB,
patch
|
anodelman
:
review+
|
Details | Diff | Splinter Review |
Looking at the config files shown in the output log, it appears shutdown tests were turned off starting at testrun id:20110412174923.
Snippet when Tshutdown was on:
tests :
- name: ts
url : startup_test/startup_test.html?begin=
url_mod : str(int(time.time()*1000))
resolution : 1
cycles : 10
timeout: 300
win_counters : []
linux_counters : []
mac_counters : []
shutdown : True
profile_path: mobile_profile
Snippet of when Tshutdown is off:
tests :
- name: ts
url : startup_test/startup_test.html?begin=
url_mod : str(int(time.time()*1000))
resolution : 1
cycles : 10
timeout: 300
win_counters : []
linux_counters : []
mac_counters : []
shutdown : False
profile_path: mobile_profile
| Assignee | ||
Updated•14 years ago
|
Group: mozilla-confidential
Whiteboard: [mobile_unittests]
| Assignee | ||
Comment 1•14 years ago
|
||
not sure where the config file is that is doing this. Could it be a buildbot step that we are configuring via perfconfigurator?
mfinkle some logfiles would be nice as well.
Group: mozilla-confidential
| Assignee | ||
Comment 2•14 years ago
|
||
simple fix to resolve missing tsshutdown output on mobile tests.
Assignee: nobody → jmaher
Attachment #526061 -
Flags: review?(anodelman)
Updated•14 years ago
|
Attachment #526061 -
Flags: review?(anodelman) → review+
| Assignee | ||
Comment 3•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
Attachment #526061 -
Attachment description: use boolean type for noShutdown, not string (1.0) → [checked in]use boolean type for noShutdown, not string (1.0)
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•