Last modified: 2014-02-12 23:55:38 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 T61738, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 59738 - New messaging lost on the way to production
New messaging lost on the way to production
Status: RESOLVED WORKSFORME
Product: MobileFrontend
Classification: Unclassified
stable (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
: browser-test-bug
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-01-06 20:55 UTC by Chris McMahon
Modified: 2014-02-12 23:55 UTC (History)
10 users (show)

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


Attachments
beta vs. production messaging for headers (90.70 KB, image/png)
2014-01-06 20:55 UTC, Chris McMahon
Details

Description Chris McMahon 2014-01-06 20:55:54 UTC
Created attachment 14237 [details]
beta vs. production messaging for headers

So on Dec 18 I checked in changes to the tests for messaging for 

* Headers https://gerrit.wikimedia.org/r/#/c/102448/
* Uploads https://gerrit.wikimedia.org/r/#/c/102450/
* Watchlist https://gerrit.wikimedia.org/r/#/c/102451/

The new messaging for Watchlist and Headers made it from beta to test2wiki to production, but the messaging for Headers did not make it all the way to prod.

(This may not be a MobileFrontend bug, reassign at will)
Comment 1 Chris McMahon 2014-01-06 20:56:32 UTC
adding Greg Grossmeier as RelEng person
Comment 2 Bingle 2014-01-06 21:05:30 UTC
Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1598
Comment 3 Chris McMahon 2014-01-06 22:52:59 UTC
This seems to be a caching problem: 

Arthur:  I can replicate the test failure manually, but if I append debug=true to the URL, I get the correct message.
Comment 4 Chris McMahon 2014-01-07 21:29:12 UTC
Does not seem to be happening any more

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


Navigation
Links