Firefox is unreliable in karma tests
Bug #1427492 reported by
Gavin Panella
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
INFO [karma]: Karma v0.12.31 server started at http://
INFO [launcher]: Starting browser Chrome
INFO [launcher]: Starting browser Firefox
INFO [launcher]: Starting browser PhantomJS
ERROR [launcher]: Cannot start Firefox
INFO [launcher]: Trying to start Firefox again (1/2).
ERROR [launcher]: Cannot start Firefox
INFO [launcher]: Trying to start Firefox again (2/2).
ERROR [launcher]: Cannot start Firefox
ERROR [launcher]: Firefox failed 2 times (cannot start). Giving up.
INFO [PhantomJS 1.9.8 (Linux)]: Connected on socket DNxUA1Crik7d8vp
INFO [Chromium 40.0.2214 (Ubuntu)]: Connected on socket WXxLaS1TY7TQ9Ha
Related branches
lp:~allenap/maas/die-firefox-die
- Gavin Panella (community): Approve
-
Diff: 16 lines (+4/-2)1 file modifiedsrc/maastesting/karma.py (+4/-2)
| tags: | added: tech-debt |
Revision history for this message
| Blake Rouse (blake-rouse) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think it is fine to have firefox disable in the unit tests. We still test with Chromium and PhantomJS. Chromium provides a much better selenium driver, because it is in tree with the Chromium source code. The Firefox webdriver is not keep in tree with the Firefox source so on new releases of Firefox it can/will break.
It safer just to have it disabled instead of make sure it always stays working.