Created attachment 759747 [details]
Since our push yesterday we've been getting a lot of validation timeouts (>100). Did something change in the AMO validator? Are timeout reasons logged somewhere?
Attached is one of the add-ons that timed out, but I can get you any others you'd like.
*** Bug 880681 has been marked as a duplicate of this bug. ***
*** Bug 880707 has been marked as a duplicate of this bug. ***
Seems to be the bug I fixed in https://github.com/mozilla/amo-validator/pull/203
*** Bug 880528 has been marked as a duplicate of this bug. ***
I am not sure whether it is the same problem, but I get "unexpected server error happened while validating" immediately (i.e., it is not timeout). See the screencast on http://mcepl.fedorapeople.org/tmp/screencast-amo-upload.webm
*** Bug 880863 has been marked as a duplicate of this bug. ***
Leaving the bug open so that we can test that this does indeed fix the issue.
Seems to be fixed now.
For me it still gets stuck at validation as I described in https://bugzilla.mozilla.org/show_bug.cgi?id=880681
Still stuck for me as well - cannot upload a new version of FireFTP. ( https://addons.mozilla.org/en-US/firefox/addon/fireftp/ )
It's fixed in the source tree, but the fixed version hasn't been pushed to production yet.
I think there's a schedule somewhere which documents when pushes of new versions of AMO happen, but it's impossible to find. Unfortunately, this page <https://wiki.mozilla.org/AMO> is years out-of-date. It would be nice if someone on the AMO dev team would update it, or at least put a link at the top to where more current information can be found.
Hm, but I see the code to commit that Matt did is only related to Jetpack addons - my addon is not a Jetpack addon so the error I'm seeing is perhaps not fixed by that?
(Besides Matt said in comment 7 he'd leave this bug open until it was fixed) I wonder if something else is going on...
You can test your add-on's submission with addons-dev.allizom.org
clouserw tentatively plans to push the fix to production on Monday.
(In reply to Mime Cuvalo from comment #12)
> Hm, but I see the code to commit that Matt did is only related to Jetpack
> addons - my addon is not a Jetpack addon so the error I'm seeing is perhaps
> not fixed by that?
Please file a separate bug and attach the XPI that fails.
Cool, thanks for your help, Matt. Indeed it's working on allizom.org. Strange that it's somehow my addon would be related to Jetpack validation but that's a separate question ^_^. Thanks again!
*** Bug 880952 has been marked as a duplicate of this bug. ***
*** Bug 880978 has been marked as a duplicate of this bug. ***
*** Bug 881300 has been marked as a duplicate of this bug. ***
I will mark it as verified since I was able to validate more add-ons on -dev.