Britney flops back and forth between Running and Approved a lot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bileto |
Fix Released
|
Critical
|
Martin Pitt | ||
britney |
Fix Released
|
High
|
Martin Pitt |
Bug Description
It seems as though any silo which would run a unity8 autopkgtest often flips back and forth between Running and Approved, eg:
https:/
2016-01-25 10:35:40 -0800 (britney-bot) britney_signoff: Running
2016-01-24 18:39:23 -0800 (britney-bot) britney_signoff: Approved
2016-01-24 17:07:26 -0800 (britney-bot) britney_signoff: Running
2016-01-23 01:58:31 -0800 (britney-bot) britney_signoff: Approved
2016-01-22 16:16:51 -0800 (britney-bot) britney_signoff: Running
2016-01-22 14:46:48 -0800 (britney-bot) britney_signoff: Approved
2016-01-22 13:11:09 -0800 (britney-bot) britney_signoff: Running
2016-01-21 13:50:24 -0800 (britney-bot) britney_signoff: Approved
2016-01-21 11:16:16 -0800 (britney-bot) britney_signoff: Running
2016-01-21 09:18:31 -0800 (britney-bot) britney_signoff: Approved
2016-01-21 08:03:20 -0800 (britney-bot) britney_signoff: Running
2016-01-19 17:30:56 -0800 (britney-bot) britney_signoff: Approved
2016-01-19 07:18:21 -0800 (britney-bot) britney_signoff: Running
2016-01-18 23:46:16 -0800 (britney-bot) britney_signoff: Approved
2016-01-18 20:47:04 -0800 (britney-bot) britney_signoff: Running
2016-01-18 20:07:36 -0800 (britney-bot) britney_signoff: Approved
2016-01-18 18:45:21 -0800 (britney-bot) britney_signoff: Running
2016-01-18 11:51:37 -0800 (britney-bot) britney_signoff: Approved
2016-01-18 08:41:17 -0800 (britney-bot) britney_signoff: Running
2016-01-18 07:28:07 -0800 (pete-woods) lander_signoff: Approved
2016-01-14 07:47:46 -0800 (ci-train-bot) Successfully built
So looking at the timestamps, that's over a period of 8 days that it continuously re-runs the tests without there being any new package builds in the silo.
I would guess that the autopkgtest infrastructure is not correctly isolating silo builds and, eg, when one silo triggers a unity8 autopkgtest, all unity8-related silos get re-run.
This is probably really wasteful of autopkgtest resources and it'd be good if silos autopkgtest results were not affected by tests run in other silos.
Related branches
Changed in britney: | |
assignee: | nobody → Martin Pitt (pitti) |
Changed in bileto: | |
assignee: | nobody → Robert Bruce Park (robru) |
Changed in bileto: | |
assignee: | Robert Bruce Park (robru) → Martin Pitt (pitti) |
Changed in britney: | |
status: | Incomplete → In Progress |
Changed in britney: | |
status: | Fix Committed → In Progress |
Currently happening with these three tickets:
12:37:15 <queuebot> boiko artmello tiagosh, https:/ /requests. ci-train. ubuntu. com/#/ticket/ 696 QA Signoff: Ready /requests. ci-train. ubuntu. com/#/ticket/ 910 QA Signoff: Ready /requests. ci-train. ubuntu. com/#/ticket/ 872 QA Signoff: Ready /requests. ci-train. ubuntu. com/#/ticket/ 696 QA Signoff: Required /requests. ci-train. ubuntu. com/#/ticket/ 910 QA Signoff: Required /requests. ci-train. ubuntu. com/#/ticket/ 872 QA Signoff: Required
12:37:15 <queuebot> dobey, https:/
12:37:16 <queuebot> pete-woods, https:/
13:17:57 <queuebot> boiko artmello tiagosh, https:/
13:17:58 <queuebot> dobey, https:/
13:17:58 <queuebot> pete-woods, https:/
And when I look through the excuses files, it's always unity8 in xenial on armhf that is "running"