Closed
Bug 562027
Opened 15 years ago
Closed 15 years ago
Make sure to execute Mozmill test-runs sequentially and not in parallel
Categories
(Mozilla QA Graveyard :: Mozmill Automation, defect)
Mozilla QA Graveyard
Mozmill Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
Right now it can happen that the test-run for Firefox 3.6 on the qa-mozmill box gets executed while the former test-run for Firefox 3.5 hasn't been finished yet.
We have to make sure that such a situation doesn't happen anymore, because it will cause some orange test results. The new test-run will remove the focus from the Firefox 3.5 window and tests fail. The reason is that Mozmill tests can only be executed in the front-most application.
We should only have 1 entry in our crontab which executes tests for 3.5, 3.6, and the upcoming 3.7 in a row, and not multiple entries which can cause test-runs to be executed in parallel.
Assignee | ||
Updated•15 years ago
|
Whiteboard: [mozmill-automation]
Assignee | ||
Updated•15 years ago
|
Assignee | ||
Comment 1•15 years ago
|
||
Clint, I have put a couple of patches onto your review queue (pull requests). For now I will have to wait on your input before I can continue to port the used scripts on our qa-mozmill machine over to the ones we have on Github now.
It would be great if you can go through the review queue this week, so we can have an active Firefox 3.7 test-run by end of this week. Thanks!
Assignee | ||
Comment 2•15 years ago
|
||
(In reply to comment #1)
> It would be great if you can go through the review queue this week, so we can
> have an active Firefox 3.7 test-run by end of this week. Thanks!
Those are all the commits back to 2010-05-07 on my firefox-automation branch:
http://github.com/whimboo/mozmill/commits/firefox-automation
Assignee | ||
Comment 3•15 years ago
|
||
This has been solved with my work on the above given branch. We can now run the tests against all builds in a sequential order. I only have to create a script now which runs all those test-runs in the wanted order:
* software updates
* bft - normal tests
* bft - restart tests
* and others in the future...
Assignee | ||
Comment 4•15 years ago
|
||
I uploaded a combined test-run script which will execute all the tests in a row:
http://github.com/whimboo/mozmill/commit/a14d45d07b389269f59031035f42f7f4d051aa48
The only limitation for now is that it will uninstall the builds (if installers have been specified) between each test-run. But that's not a problem for now and I will fix it later so we run tests even against the updated build (first test-run).
Assignee | ||
Comment 5•15 years ago
|
||
Jeff, would be nice if you could find the time for a quick review, so I could prepare our machine tomorrow morning to be able to run all tests.
Assignee | ||
Comment 6•15 years ago
|
||
Merged to master.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 7•14 years ago
|
||
Move of Mozmill related project bugs to newly created components. You can
filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Component: Mozmill → Mozmill Automation
Product: Testing → Mozilla QA
QA Contact: mozmill → mozmill-automation
Whiteboard: [mozmill-automation]
Version: Trunk → unspecified
Updated•11 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•