588397 - [tracking bug] Test updates on nightlies

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P5)

Description

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

(6:38:39 AM) bhearsum|buildduty: so
(6:38:52 AM) bhearsum|buildduty: when the nightly build finishes, you want it to trigger a test that:
(6:38:59 AM) bhearsum|buildduty: - downloads the previous nightly
(6:39:03 AM) bhearsum|buildduty: - updates to the current one
(6:39:05 AM) bhearsum|buildduty: - runs unit tests
(6:39:25 AM) khuey: right
(6:39:52 AM) bhearsum|buildduty: there's a couple tricky bits in there, but i don't _think_ there's any huge issues
(6:39:59 AM) khuey: cool

Update-verify is probably 95% of the benefit with 2% of the work, but this would be the ideal situation IMHO.

Comment 1

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

601469 is a good example of the things this could catch (and that, AIUI, update verify would not catch).

Comment 2

[Mike Shaver (:shaver emeritus)]

I actually don't care if the nightly fails every unit test.  I care that it can start up and check for + apply updates, pretty much everything else is fair game.  The UI can be one big yellow screen of death, whatever -- just make sure that we don't break updates (a third time?).

Comment 3

[Aki Sasaki (not active)]

We have startup tests on nightly now.