407430 - Sisyphus - failure to install or initialize Spider should cause run to fail

Status: RESOLVED FIXED

(Testing Graveyard :: Sisyphus, defect)

Description

[Bob Clary [:bc] (inactive)]

Currently if Spider fails to install, the install-extensions-*.html time out, or if the Spider check page fails with a time out the frame work will not terminate and will attempt to run even though Spider is not available. This will cause each test page to be loaded into a normal browser window which will not close on its own thus causing every test to time out and the test run to take _forever_. If Spider installation or initialization fails, then the test run should fail immediately.

Comment 1

[Bob Clary [:bc] (inactive)]

Attachment: JavaScript Tests patch

Comment 2

[Bob Clary [:bc] (inactive)]

Attachment: Sisyphus patch

Comment 3

[Rob Campbell [:rc] (:robcee)]

Comment on attachment 292409 [details] [diff] [review]
Sisyphus patch

these look good to me

Comment 4

[Bob Clary [:bc] (inactive)]

Checking in bin/install-extensions.sh;
/cvsroot/mozilla/testing/sisyphus/bin/install-extensions.sh,v  <--  install-extensions.sh
new revision: 1.4; previous revision: 1.3
done
Checking in bin/smoke-build.sh;
/cvsroot/mozilla/testing/sisyphus/bin/smoke-build.sh,v  <--  smoke-build.sh
new revision: 1.4; previous revision: 1.3
done
Checking in bin/test-setup.sh;
/cvsroot/mozilla/testing/sisyphus/bin/test-setup.sh,v  <--  test-setup.sh
new revision: 1.6; previous revision: 1.5
done
Checking in bin/tester.sh;
/cvsroot/mozilla/testing/sisyphus/bin/tester.sh,v  <--  tester.sh
new revision: 1.7; previous revision: 1.6
done
Checking in runtests.sh;
/cvsroot/mozilla/js/tests/runtests.sh,v  <--  runtests.sh
new revision: 1.8; previous revision: 1.7
done

Comment 5

[(not currently active) Ted Mielczarek]

Mass move of Sisyphus bugs to Testing : Sisyphus. Filter on SisyphusMassMove to ignore.