Last modified: 2013-02-25 22:24:37 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 T47156, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45156 - Guided Tour does not work at test2
Guided Tour does not work at test2
Status: VERIFIED FIXED
Product: MediaWiki extensions
Classification: Unclassified
GuidedTour (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-19 17:02 UTC by Željko Filipin
Modified: 2013-02-25 22:24 UTC (History)
6 users (show)

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


Attachments

Description Željko Filipin 2013-02-19 17:02:22 UTC
Chris and I paired on browser tests for guided tour last week. The tests run at test2 and they were passing. I have just noticed that they are failing, and it looks like guided tour is not working at test2.

Failed tests for Chrome:

https://wmf.ci.cloudbees.com/job/browsertests-linux-chrome/lastCompletedBuild/testReport/

Sauce Labs job with screen shots and video of the test run:

https://saucelabs.com/jobs/bc8dd01eb2d54b14b37609761bfe59ce

Example page:

http://test2.wikipedia.org/wiki/Uranus?tour=gettingstarted
Comment 1 Chris McMahon 2013-02-19 17:19:24 UTC
This should be on mediawiki.org also but is not http://www.mediawiki.org/wiki/Editor_engagement_experiments/Prioritization?tour=gettingstarted
Comment 2 Željko Filipin 2013-02-19 21:12:16 UTC
Looks like this is fixed now.
Comment 3 Matthew Flaschen 2013-02-19 22:39:10 UTC
This was a deployment issue.

GuidedTour uses a submodule, and when the 1.21wmf10 branch was cut, they did not clone with --recursive.

I fixed it (at least for this branch) earlier by doing a submodule update --init and a sync-dir.

I think this is actually an issue with the script that cuts the branches, which I'm going to follow up on (I've also made Ryan Faulkner, one of the git-deploy people, aware of this).
Comment 4 Matthew Flaschen 2013-02-25 22:24:37 UTC
This should be fixed properly by https://gerrit.wikimedia.org/r/#/c/50467/, at least until we switch to git-deploy (but they are aware of it too).

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


Navigation
Links