Last modified: 2014-01-29 15:03:16 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T61174, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 59174 - Mobile tests report Firefox profile problem
Mobile tests report Firefox profile problem
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Quality Assurance (Other open bugs)
unspecified
All All
: High major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-31 23:20 UTC by Chris McMahon
Modified: 2014-01-29 15:03 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Chris McMahon 2013-12-31 23:20:37 UTC
Upon running a test in my local environment e.g. 

r$ bundle exec cucumber features/footer.feature 
Using the default profile...
Success: created profile 'NearbyProfile /tmp/NearbyProfile/' at '/tmp/NearbyProfile/prefs.js'

Firefox executes the test but then hangs with a modal dialog that says "Profile missing/Your Firefox profile cannot be loaded. It may be missing or inaccessible."  

This causes the next scenario not to run until the modal dialog is dismissed manually.
Comment 1 Chris McMahon 2014-01-01 00:15:59 UTC
more information: 

* search.feature, external_links.feature and image_resolves.feature do not cause the error message in my local environment

"export BROWSER_LABEL=chrome" has no effect.  Even though the env var is set properly, the tests all run in Chrome regardless. 

Note that the Cloudbees builds of the current code seem to be fine:  this test is clearly running Chrome and it fails for a real reason:  https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome/171/testReport/(root)/Upload%20image/Upload_image_file/

Finally, OS could be a factor:  I am on Linux, but Jon Robson on a Mac fails to launch any browser at all, and gets no error message.
Comment 2 Chris McMahon 2014-01-01 00:18:20 UTC
The culprit is likely the new Nearby code:  https://gerrit.wikimedia.org/r/#/c/101129/
Comment 3 Gerrit Notification Bot 2014-01-02 18:26:37 UTC
Change 104997 had a related patch set uploaded by Cmcmahon:
Revert "QA: New browser test for "Nearby" page". This is causing several issues for Bug 59174

https://gerrit.wikimedia.org/r/104997
Comment 4 Chris McMahon 2014-01-02 18:52:59 UTC
For linux, the issue is that the new code to create a profile for the browser only works on the first Scenario, and tests with more than one Scenario incur the "cannot be loaded" error.  

I'm not sure what the issue is on Mac, but Jon Robson reports that no browser is ever started.
Comment 5 Gerrit Notification Bot 2014-01-02 22:13:44 UTC
Change 104997 merged by jenkins-bot:
Revert "QA: New browser test for "Nearby" page". This is causing several issues for Bug 59174

https://gerrit.wikimedia.org/r/104997
Comment 6 Gerrit Notification Bot 2014-01-03 20:24:49 UTC
Change 105253 had a related patch set uploaded by Cmcmahon:
Revert "Revert "QA: New browser test for "Nearby" page". This is causing several issues for Bug 59174"

https://gerrit.wikimedia.org/r/105253
Comment 7 Gerrit Notification Bot 2014-01-03 21:50:17 UTC
Change 105253 abandoned by Cmcmahon:
Revert "Revert "QA: New browser test for "Nearby" page". This is causing several issues for Bug 59174"

Reason:
Salvage operation over!

https://gerrit.wikimedia.org/r/105253
Comment 8 Željko Filipin 2014-01-29 14:07:10 UTC
Is this fixed?
Comment 9 Chris McMahon 2014-01-29 15:03:16 UTC
Resolved by handling the Nearby profile as a special case

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links