1168640 - Twitter feed is missing on dev after deploy

Status: RESOLVED FIXED

(www.mozilla.org :: Bedrock, defect)

Description

[Stephen Donner [:stephend] Not actively reading bugmail]

Between these two builds:

1) Success
#2​43​​9
May 26, 2015 1:19 PM


2) Failed
#2​44​​0
May 26, 2015 1:49 PM
 
the Twitter feed on the promo portion of Mozilla.org's homepage on dev (https://www-dev.allizom.org) went missing, and caused our automation to fail:

https://webqa-ci.mozilla.com/view/Mozilla.org/job/mozilla.org.dev.saucelabs/2440/


tests/test_home.py:20: in test_promo_links_are_valid
url = home_page.link_destination(link.get('locator'))
pages/desktop/base.py:27: in link_destination
link = self.selenium.find_element(*locator)
.env/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py:664: in find_element
{'using': by, 'value': value})['value']
.env/lib/python2.7/site-packages/selenium/webdriver/remote/webdriver.py:175: in execute
self.error_handler.check_response(response)
.env/lib/python2.7/site-packages/selenium/webdriver/remote/errorhandler.py:166: in check_response
raise exception_class(message, screen, stacktrace)
E   NoSuchElementException: Message: Unable to locate element: {"method":"css selector","selector":"#promo-16 .twt-actions a:nth-child(1)"}
E   For documentation on this error, please visit: http://seleniumhq.org/exceptions/no_such_element.html
E   Build info: version: '2.43.0', revision: '597b76b', time: '2014-09-09 20:52:14'
E   System info: host: 'WIN-R1JBAO1CNPS', ip: '172.20.40.49', os.name: 'Windows Server 2008 R2', os.arch: 'x86', os.version: '6.1', java.version: '1.7.0_60'
E   Driver info: driver.version: unknown
E   Stacktrace:
E       at <anonymous class>.FirefoxDriver.prototype.findElementInternal_ (file:///C:/Users/ADMINI~1/AppData/Local/Temp/anonymous964796505423391404webdriver-profile/extensions/[e-mail]/components/driver-component.js:9618:26)
E       at <anonymous class>.fxdriver.Timer.prototype.setTimeout/<.notify (file:///C:/Users/ADMINI~1/AppData/Local/Temp/anonymous964796505423391404webdriver-profile/extensions/[e-mail]/components/driver-component.js:548:5)

Sauce Labs job: http://saucelabs.com/jobs/53e091d6d8e84a3d9803e3b40c4313bb

(:jgmize is working on fixing this, but wanted to get it filed to see if it's a one-time failure, or something we can help avoid in the future.)

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

As a datapoint, it looks like some script/cron job ran, and repopulated the Twitter feed, between:

Failed:

#2​44​​8
May 26, 2015 6:49 PM
https://webqa-ci.mozilla.com/view/Mozilla.org/job/mozilla.org.dev.saucelabs/2448/

Fixed:

#2​44​​9
May 26, 2015 7:49 PM
https://webqa-ci.mozilla.com/view/Mozilla.org/job/mozilla.org.dev.saucelabs/2449/

Comment 2

[Josh Mize [:jgmize]]

The twitter feed is updated on dev and demo environments during deployment after the dev DB is completely wiped and recreated, so if there is a network glitch or other issue during the deploy the twitter feed(s), blog feed(s), and/or release notes can go missing until the next deployment. On dev, this happens automatically every time a new commit is pushed to the master branch, and we can also do this manually via chief. I did a manual push last night after the test failures, which resolved the issue. This will continue to be periodically necessary unless and until we choose a different strategy for dev and demo deploys, but for obvious reasons, we don't wipe the DB on deploy to stage or prod environments so this isn't a major issue, IMO. I'm going to go ahead and mark this as FIXED for now, but feel free to reopen and/or add further comments when this happens again.

Comment 3

[Stephen Donner [:stephend] Not actively reading bugmail]

We had a test-automation failure at 3:07pm PDT due to this, and Josh tried to fix:

3:07 PM <webqatestbot> Project mozilla.org.dev.saucelabs build #3451: FAILURE in 17 min: https://webqa-ci.mozilla.com/job/mozilla.org.dev.saucelabs/3451/
4:11 PM <•jgmize> hrm, running the update_tweets cron manually results in no errors but also no tweets on the dev homepage :(

Reopening for that last line as a (new?) specific failure which we should try to work out.

Comment 4

[Stephen Donner [:stephend] Not actively reading bugmail]

For posterity:

7:54 PM <webqatestbot> Project mozilla.org.dev.saucelabs build #3459: FIXED in 4 min 29 sec: https://webqa-ci.mozilla.com/job/mozilla.org.dev.saucelabs/3459/
7:59 PM  ⇐ zaach quit  ↔ lizzard nipped out  
8:13 PM — •stephend|bbiab wonders if jgmize fixed it ^^^
8:14 PM <•jgmize> stephend: yes, fixed it manually and working on a PR to fix it automatically next time

And that PR is this one: https://github.com/mozilla/bedrock/pull/3105

Comment 5

[[github robot]]

Commits pushed to master at https://github.com/mozilla/bedrock

https://github.com/mozilla/bedrock/commit/78d914e749bb8bddd5dd45b7cfafbe65ebe2740e
Update TwitterCache on save: fix bug 1168640

https://github.com/mozilla/bedrock/commit/ee4050db9f8887684c0fdcbb04f66679a9c9128c
Merge pull request #3105 from jgmize/fix-tweet-cache

Update TwitterCache on save: fix bug 1168640