MIPS build slave should run acceptance for 10 minutes with release and debug shells

VERIFIED FIXED in flash10.2.x-Spicy

Status

P3
normal
VERIFIED FIXED
8 years ago
8 years ago

People

(Reporter: brbaker, Assigned: brbaker)

Tracking

unspecified
flash10.2.x-Spicy
Other
Linux
Bug Flags:
in-testsuite +
flashplayer-qrb +
flashplayer-triage +

Details

(Whiteboard: buildbot)

Attachments

(1 attachment)

(Assignee)

Description

8 years ago
Currently the MIPS build slave will only run the "smokes" phase and that is only using the release shell. Then a full acceptance pass is done with the release and debug shells in the deep phase. We should add running 10 minutes of acceptance on the release shell using --random and then also 10 minutes with the debug shell.

This will at least give us more coverage on MIPS and still be well within current build times.
Flags: flashplayer-qrb?

Updated

8 years ago
Assignee: nobody → brbaker
Status: NEW → ASSIGNED
Flags: flashplayer-triage+
Flags: flashplayer-qrb?
Flags: flashplayer-qrb+
Priority: -- → P3
Target Milestone: --- → flash10.2.x-Spicy
(Assignee)

Comment 1

8 years ago
Created attachment 480943 [details] [diff] [review]
buildbot config to run random acceptance tests on release and debug
Attachment #480943 - Flags: review?(jsudduth)

Updated

8 years ago
Attachment #480943 - Flags: review?(jsudduth) → review+
(Assignee)

Comment 2

8 years ago
Comment on attachment 480943 [details] [diff] [review]
buildbot config to run random acceptance tests on release and debug

patch pushed as 5323:a837d40687b9
(Assignee)

Updated

8 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
(Assignee)

Updated

8 years ago
Status: RESOLVED → VERIFIED
Flags: in-testsuite+

Comment 3

8 years ago
Instead of this being random, could it be a more deterministic approach?  Here are two possibilities:

* keep track of what recent builds have tested, and cycle through all the acceptance tests in round-robin order.  

* keep track of what has failed recently, and re-test those no matter what, similar to smokes.  come to think of it, does the smokes phase rerun tests that have recently failed in the acceptance phase?  is grooming the smokes list still a manual step?

Comment 4

8 years ago
The patch does 5 mins per shell and includes 2 shells for a 10 min max.  We have more time that that.  Either increase the timeout or add additional shells.  Increasing timeout is probably best.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 5

8 years ago
Update to run 10 minutes of release and 10 minutes of debug in patch 5479:e4cce27bc2df.

NOTE: Full acceptance passes are made in the deep phase of testing.
Status: REOPENED → RESOLVED
Last Resolved: 8 years ago8 years ago
Resolution: --- → FIXED
(Assignee)

Updated

8 years ago
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.