Closed Bug 607448 Opened 14 years ago Closed 14 years ago

New add-ons can take many hours to appear

Categories

(addons.mozilla.org Graveyard :: Developer Pages, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED
5.12.3

People

(Reporter: fligtar, Assigned: jbalogh)

Details

(Whiteboard: [5.12.1.5][qa-])

We've seen a number of complaints that after submitting an add-on in the sandbox, the details page is 404 for most of the day afterwards.

I just showed Jeff an example of an add-on that was submitted 4 hours ago but still 404 because the latest version field was empty. (It's since been fixed.)
QA: I'm going to add more logging around changing current versions.  Then we can try to reproduce on prod (or wait for someone else to complain) and narrow down the cause.
Whiteboard: [5.12.1.5]
Looks like a dupe of Bug 556250?
Target Milestone: 5.12.2 → 5.12.3
Target Milestone: 5.12.3 → 4.x (triaged)
Delays of 10 or more hours for an add-on to appear are totally unacceptable. We can't bump this again.
Target Milestone: 4.x (triaged) → 5.12.3
(In reply to comment #3)
> Delays of 10 or more hours for an add-on to appear are totally unacceptable. We
> can't bump this again.

I didn't think it was still reproducible?  Jeff, what did the logging in comment 1 turn up?
I looked at the log when adblock was bumped and the current version got set at least five times before it stuck.  When I was playing with this in the shell, I couldn't see the effect of bumping a current_version on a slave until I restarted ipython.  That sounds like we have an open transaction that's not committing properly.
Calling this tentatively fixed by https://github.com/mozilla/nuggets/commit/0d369653626.  We're committing transactions after every test now, and I suspect that was the problem.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [5.12.1.5] → [5.12.1.5][qa-]
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.