Closed
Bug 490900
Opened 16 years ago
Closed 16 years ago
create a smoke test script for buildbot
Categories
(Tamarin Graveyard :: Build Config, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
flash10.1
People
(Reporter: dschaffe, Unassigned)
Details
Attachments
(2 files, 2 obsolete files)
|
19.66 KB,
patch
|
brbaker
:
review+
|
Details | Diff | Splinter Review |
|
460 bytes,
patch
|
brbaker
:
review+
|
Details | Diff | Splinter Review |
goal is to create a buildstep and blocking buildbot stage to quickly run some tests. the test list can be easily changed and may include any testsuite, performance test. if any smokes fail the testing step is not run and the build is considered failed.
- the smoketest script reads an input file containing commands to call testsuites with a specific test or group of tests
- each line of the input file is run until a time limit has been reached (e.g. 2 min)
- environment variables avmr, avmd, avmrd, avmdd represent shell builds, all builds should be tested
- the test list can be changed to include any recent failures to regression test
Flags: flashplayer-triage+
| Reporter | ||
Comment 1•16 years ago
|
||
Attachment #375226 -
Flags: review?(brbaker)
| Reporter | ||
Comment 2•16 years ago
|
||
new attachment changes input file format to: cd ./acceptance; ./runtests.py ...
using, subprocess.Popen shell=True, setting cwd is not necessary, cd sets the directory and wildcards for test filenames works. This format is better since failures can be easily reproduced by pasting the commands.
I will add another patch for a separate winmobile smoketest buildbot script and input file, the script will deploy the release shell on the device and set AVM to the ceremoteshell.
Attachment #375226 -
Attachment is obsolete: true
Attachment #375338 -
Flags: review?(brbaker)
Attachment #375226 -
Flags: review?(brbaker)
Updated•16 years ago
|
Attachment #375338 -
Flags: review?(brbaker) → review+
Comment 3•16 years ago
|
||
Comment on attachment 375338 [details] [diff] [review]
patch2
suggest breaking apart some of the groups, such as running all of mmgc as "one" test. This caused my machine to actually run for 3:03 instead of 2:00 since it run the mmgc tests with a debug VM for over a minute.
| Reporter | ||
Comment 4•16 years ago
|
||
broke up the groups further to avoid large runs. Made a few other minor fixes. submitted in 1821 : 7d814d0d98cc
| Reporter | ||
Comment 5•16 years ago
|
||
patch to produce 1 pass or 1 fail per smoke test line in runsmokes.txt instead of aggregating passes and fails.
Attachment #375613 -
Flags: review?(brbaker)
Comment 6•16 years ago
|
||
Comment on attachment 375613 [details] [diff] [review]
patch to make 1 pass or 1 fail per test
This seems like you could increment the pass and the fail at the same time, they need to be exclusive, if there is a single fail, then it is a fail, even if there is a pass.
Attachment #375613 -
Flags: review?(brbaker) → review-
| Reporter | ||
Comment 7•16 years ago
|
||
update to patch. We already made sure if passes==0 increment fails. changed to else should work so each test in smoketest is 1 pass or 1 fail.
Attachment #375613 -
Attachment is obsolete: true
Attachment #375618 -
Flags: review?(brbaker)
Updated•16 years ago
|
Attachment #375618 -
Flags: review?(brbaker) → review+
Status: NEW → ASSIGNED
Flags: flashplayer-qrb+
Priority: -- → P3
Target Milestone: --- → flash10.x
| Reporter | ||
Comment 8•16 years ago
|
||
patched pushed.
Status: ASSIGNED → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•