Confirmed users
2,197
edits
QA/Execution/Web Testing/Meetings/2012-05-31: Difference between revisions
QA/Execution/Web Testing/Meetings/2012-05-31 (view source)
Revision as of 15:44, 31 May 2012
, 31 May 2012→Discussion Items / Updates
| Line 17: | Line 17: | ||
** Documentation! | ** Documentation! | ||
* Need help getting the new-user registration flow back up on [https://github.com/mozilla/browserid-tests browserid-tests], against dev.123done.org and beta123done.org, using [https://github.com/davehunt/bidpom BIDPOM]. | * Need help getting the new-user registration flow back up on [https://github.com/mozilla/browserid-tests browserid-tests], against dev.123done.org and beta123done.org, using [https://github.com/davehunt/bidpom BIDPOM]. | ||
** Should be simple - create staging & production branches for browserid-tests, [https://github.com/davehunt/bidpom/wiki/Using-BIDPOM-as-a-submodule update BIDPOM in these branches to use the appropriate versions], and update staging & master branches to use new registration flow as shown in [https://github.com/davehunt/bidpom/blob/master/tests/webdriver/check_sign_in.py#L49 the tests]. | ** <strike>Should be simple - create staging & production branches for browserid-tests, [https://github.com/davehunt/bidpom/wiki/Using-BIDPOM-as-a-submodule update BIDPOM in these branches to use the appropriate versions], and update staging & master branches to use new registration flow as shown in [https://github.com/davehunt/bidpom/blob/master/tests/webdriver/check_sign_in.py#L49 the tests].</strike> | ||
** Done: | |||
*** [https://github.com/mozilla/BrowserID-Tests/pull/19 Pull for staging/beta] | |||
*** [https://github.com/mozilla/BrowserID-Tests/pull/20 Pull for master/dev] | |||
*** Once merged all Jenkins jobs will need to be updated to pull from the appropriate branch. | |||
* Stalled builds are back, and now we have the backup plugin there's a new side-effect: the plugin prepares Jenkins for shutdown before a backup, but waits for all jobs to complete (and enforces 'quiet node' after waiting 2 hours). If there are stalled jobs then Jenkins is essentially doing nothing until the jobs are aborted. I think we may need to investigate using the [http://pypi.python.org/pypi/pytest-timeout pytest-timeout] plugin, however it currently clashes with pytest-mozwebqa. For now I have re-enabled abort for amo.dev and marketplace.dev. | * Stalled builds are back, and now we have the backup plugin there's a new side-effect: the plugin prepares Jenkins for shutdown before a backup, but waits for all jobs to complete (and enforces 'quiet node' after waiting 2 hours). If there are stalled jobs then Jenkins is essentially doing nothing until the jobs are aborted. I think we may need to investigate using the [http://pypi.python.org/pypi/pytest-timeout pytest-timeout] plugin, however it currently clashes with pytest-mozwebqa. For now I have re-enabled abort for amo.dev and marketplace.dev. | ||
* After investigating the above, I noticed that the backups were failing. This was due to the drive they are backed up to not being mounted. I have fixed this, but it should be a buildmaster responsibility to ensure backups are successful. | * After investigating the above, I noticed that the backups were failing. This was due to the drive they are backed up to not being mounted. I have fixed this, but it should be a buildmaster responsibility to ensure backups are successful. | ||