FYI bot test-results-upload stages all seem to be failing |
||||
Issue descriptionLooking at the logs for the upload-to-test-results step from https://build.chromium.org/p/chromium.fyi/builders/Fuchsia%20%28dbg%29/builds/16224 it looks like the uploader is getting an HTTP 400 response from the server.
,
Feb 14 2018
"test_results_uploader.PermanentError: Received HTTP status 400 loading "https://test-results-test.appspot.com/testfile/upload": strconv.Atoi: parsing "null": invalid syntax" sounds like it's trying to upload something ... interesting.
,
Feb 14 2018
Actually, if this is a chromium.linux/chromium.fyi split, it could be due to the differences between test-results and test-results-test. It also appears that this is happening beyond the fuchsia FYI bots; updating the title accordingly. +seanmccullough: looks like you've got a tainted version on test-results-test; any idea if that could be related to this?
,
Feb 14 2018
taking a look... Also, I've been curious - who is posting to test-results-test instead of test-results? Any why?
,
Feb 14 2018
passing this over since you're looking at it; feel free to pass it back if it isn't something server-side. As for what's uploading to the staging instance: FYI bots (what better to use the staging instance) & is_experimental builds for luci conversion (to avoid poisoning the actual results uploaded by parallel non-experimental builds), along with some random bots (possibly things that have migrated from FYI?)
,
Feb 14 2018
Ok. [I think we should try to support those use cases in ShamWow without having to point them at an entirely different instance, so I may have more questions about this later.]
,
Feb 14 2018
Pushed a non-tainted version. Waiting for more /testfile/upload attempts. Looks like the latest build hasn't gotten to test uploads yet: https://ci.chromium.org/buildbot/chromium.fyi/Fuchsia%20(dbg)/16226
,
Feb 14 2018
Upload steps are succeeding now. |
||||
►
Sign in to add a comment |
||||
Comment 1 by w...@chromium.org
, Feb 14 2018