Closed Bug 1023031 Opened 10 years ago Closed 10 years ago

No 'ready for releasetest testing' email for Firefox 30.0 build2

Categories

(Release Engineering :: Release Automation: Other, defect, P1)

x86
All
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

References

Details

We pushed to the mirrors, got 'completed start_uptake_monitoring', but no 'ready for releasetest testing'.

Turns out bouncer is giving us 400 responses when we try to check
https://bounceradmin.mozilla.com/api/uptake/?product=Firefox-30.0-Partial-30.0&os=linux
https://bounceradmin.mozilla.com/api/uptake/?product=Firefox-30.0-Partial-30.0&os=linux64
https://bounceradmin.mozilla.com/api/uptake/?product=Firefox-30.0-Partial-30.0&os=osx
https://bounceradmin.mozilla.com/api/uptake/?product=Firefox-30.0-Partial-30.0&os=win

These are unusual, and stem from a communication issue that meant we got 30.0 build1 put in the list of partials in ship-it.
Assignee: nobody → nthomas
Priority: -- → P1
We don't have any build1 -> build2 snippets, because that failed in the updates builder (also fallout from 30.0build1 in list of partials). So no need for a Firefox-30.0-Partial-30.0 product.

I'll just create the product and 4 locations to satisfy the uptake checker, then delete them again.
Which worked, up until the point we got an exception:

2014-06-09 20:12:16-0700 [HTTPPageGetter,client] TriggerBouncerCheck: uptake is 10071
2014-06-09 20:12:16-0700 [HTTPPageGetter,client] TriggerBouncerCheck: Stopping uptake monitoring: Reached required uptake: 10071
2014-06-09 20:12:16-0700 [HTTPPageGetter,client] TriggerBouncerCheck failed:
	Traceback (most recent call last):
	  File "/builds/buildbot/build1/lib/python2.7/site-packages/twisted/internet/defer.py", line 441, in _runCallbacks
	    self.result = callback(self.result, *args, **kw)
	  File "/builds/buildbot/build1/lib/python2.7/site-packages/twisted/internet/defer.py", line 664, in _cbDeferred
	    self.callback(self.resultList)
	  File "/builds/buildbot/build1/lib/python2.7/site-packages/twisted/internet/defer.py", line 318, in callback
	    self._startRunCallbacks(result)
	  File "/builds/buildbot/build1/lib/python2.7/site-packages/twisted/internet/defer.py", line 424, in _startRunCallbacks
	    self._runCallbacks()
	--- <exception caught here> ---
	  File "/builds/buildbot/build1/lib/python2.7/site-packages/twisted/internet/defer.py", line 441, in _runCallbacks
	    self.result = callback(self.result, *args, **kw)
	  File "/builds/buildbot/build1/lib/python2.7/site-packages/buildbotcustom/scheduler.py", line 346, in checkUptake
	    Triggerable.trigger(self, self.ss, self.set_props)
	  File "/builds/buildbot/build1/lib/python2.7/site-packages/buildbot-0.8.2_hg_8a9e33843c3f_production_0.8-py2.7.egg/buildbot/schedulers/triggerable.py", line 66, in trigger
	    d = self.parent.db.runInteraction(self._trigger, ss, props)
	exceptions.AttributeError: 'NoneType' object has no attribute 'db'
I'm speculating that a reconfig may have happened after the initial uptake check started. I forced the release-mozilla-release-start_uptake_monitoring builder and back in action.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.