Closed
Bug 525263
Opened 16 years ago
Closed 16 years ago
add maemo test coverage for all branches + try
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 538517
People
(Reporter: mozilla, Assigned: jhford)
References
Details
Attachments
(2 files)
|
19.44 KB,
patch
|
mozilla
:
review-
|
Details | Diff | Splinter Review |
|
1.96 KB,
patch
|
mozilla
:
review+
|
Details | Diff | Splinter Review |
I think this is a q4 goal.
| Reporter | ||
Comment 1•16 years ago
|
||
John: for Try, could you make sure the sendchange specifies that the branch is "try" (or some variant)? We need to send the info to graphs-stage instead of graphs.m.o and the tinderbox page should be MozillaTry instead of Mobile or Tracemonkey.
| Reporter | ||
Comment 2•16 years ago
|
||
probably needs to have 'maemo' in the branch too; don't want to trigger incoming winmo tests with maemo try builds. "maemo-try"?
| Reporter | ||
Comment 3•16 years ago
|
||
John: joduinn pointed out you should probably talk w/ lsblakk and bhearsum about the large Try refactor going on currently.
| Assignee | ||
Comment 4•16 years ago
|
||
i have the *-mobile-master side work done I think.
Lukas, Ben,
what is the plan for mobile try builders?
Assignee: aki → jford
Comment 5•16 years ago
|
||
I don't think the first pass on try-as-a-branch is going to change how we do mobile builds on try. So, implement it whichever way is best for you. When we convert the try mobile stuff over to mobile_config.py/mobile_master.py we can deal with moving all of the mobile stuff over at once.
| Assignee | ||
Comment 6•16 years ago
|
||
These are the buildbot-configs changes that create a maemo-try branch. It also adds a switch to enable/disable queue collapsing on unittests and talos runs.
This is not complete as I need to add to the build factory the commands to build the packaged tests and uploading them alongside the other build artifacts. I have test runs that have been built as nightlies (and known to work) running through these factories right now to test that mobile-master side code works.
I have only made the changes on mobile-staging. I will copy the changes over to mobile on an r+
With the location that builds are uploaded to, we need to ignore self signed certificates which is done in the soon to be accompanying buildbotcustom patch
Attachment #418244 -
Flags: review?(aki)
| Assignee | ||
Comment 7•16 years ago
|
||
We need this to disable checking ssl certificates for package urls.
We will need to run:
sed -i -e 's/wget/wget --no-check-certificate/' /tools/maemkit/hackTestUrl.sh
on all the slaves to make sure that the packaged test files get uploaded as well
Attachment #418247 -
Flags: review?(aki)
| Reporter | ||
Comment 8•16 years ago
|
||
Comment on attachment 418244 [details] [diff] [review]
mobile-try-configs-mobile-master.diff
>+BRANCHES['mobile-try']['platforms']['n810']['talos_branch'] = 'maemo-try'
This should be MozillaTest:
FAIL: Failed to send data 5 times... quitting
RETURN:send failed, graph server says:
RETURN:No branch_id for a branch_name 'maemo-try' can be found
We also need mail notifications for Try.
I'd also like to see the mobile/ configs -- I know it's a pain maintaining both while in active development, but I want to make sure the tinderbox/graphserver/etc. bits are right.
Other than that I'm glad to see this is working =)
Attachment #418244 -
Flags: review?(aki) → review-
| Reporter | ||
Updated•16 years ago
|
Attachment #418247 -
Flags: review?(aki) → review+
| Assignee | ||
Comment 9•16 years ago
|
||
Yep, i have that change locally, i forgot to include it in the patch.
As discussed in IRC, is it ok for me to get the jobs working now and get the mail notifications as a follow up?
| Reporter | ||
Comment 10•16 years ago
|
||
I'd say put it all in if a) it's relatively quick (a few days?) and b) I weren't going on vacation soon, especially since this will probably tie up mobile devices with no one paying attention otherwise. But I am, and it would be good to see these running, so sure.
| Assignee | ||
Comment 11•16 years ago
|
||
All of the work for this bug is going to be done as part of the config rewrite in bug 538517.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
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
•