Closed
Bug 598153
Opened 14 years ago
Closed 14 years ago
Trigger Two More Talos Builds
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sdwilsh, Assigned: armenzg)
References
Details
I need two more talos builds triggered for this changeset:
http://hg.mozilla.org/projects/places/rev/c4f8232c7aef
The tests I need ran are:
tp4
tp4_memset
tp4_pbytes
tp4_rss
tp4_shutdown
tp4_xres
ts
ts_cold
ts_cold_generated_ma
ts_cold_generated_max_shutdown
ts_cold_generated_med
ts_cold_generated_med_shutdown
ts_cold_generated_min
ts_cold_generated_min_shutdown
ts_cold_shutdown
ts_places_generated_max
ts_places_generated_max_shutdown
ts_places_generated_med
ts_places_generated_med_shutdown
ts_places_generated_min
ts_places_generated_min_shutdown
ts_shutdown
twinopen
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → armenzg
Status: NEW → ASSIGNED
Assignee | ||
Updated•14 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•14 years ago
|
||
I am trying to figure this out by looking at:http://hg.mozilla.org/build/buildbot-configs/file/701b6ccd8e55/mozilla-tests/config.py#l19Which talos suites do you want out of these?* nochrome* cold* dromaeo* a11y* svg* chrome* tp4* dirty* scrollFrom looking at the code I believe you want cold, tp4 and dirty but I am really not sure.And also for which platforms is this for?
Priority: P2 → --
Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1)
all platforms; chrome, dirty, tp4, cold
Reporter | ||
Comment 3•14 years ago
|
||
Builds and symbols are now stored here since tinderbox is going to nuke them soon:
http://files.shawnwilsher.com/changesets/c4f8232c7aef/
Assignee | ||
Comment 4•14 years ago
|
||
I have trigger double jobs for each platform for the 4 talos suites you
mention.
Let me know if I did what you needed and if it run properly.
I forgot about the tinderbox-builds clean up rule and many things had popped up last night.
It seems that the build was still around as the jobs managed to download the build.
Assignee | ||
Comment 5•14 years ago
|
||
I believe the jobs have completed correctly.
Let me know if it didn't.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 6•14 years ago
|
||
(In reply to comment #5)
> I believe the jobs have completed correctly.
> Let me know if it didn't.
Looks like the graph server only knows about a total of two runs and not three.
Reporter | ||
Comment 7•14 years ago
|
||
To be more clear, the tp4 and twinopen tests only seem to have two runs.
Comment 8•14 years ago
|
||
Armen, your requests probably got merged. The only guaranteed way is to sendchange/force then wait for those builds to start before doing it again. Painful.
Assignee | ||
Comment 9•14 years ago
|
||
(In reply to comment #8)
> Armen, your requests probably got merged. The only guaranteed way is to
> sendchange/force then wait for those builds to start before doing it again.
> Painful.
shoot. I looked at http://cruncher.build.mozilla.org/buildapi/revision/places/c4f8232c7aef and filtered by "tp4 09-21" and saw 2 jobs per suite but I noticed that the time running each one shows that both entries had the same time and therefore it shows that they were merged. Re-triggering again.
Assignee | ||
Updated•14 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 10•14 years ago
|
||
I believe (from eye-balling and comparing running times) that we have run all the requested suites for all platforms twice.
Let me know if this incorrect.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
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
•