Test results upload 400s |
||||
Issue descriptionI think this manifests itself here: https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.linux%2FLinux_Tests%2F49891%2F%2B%2Frecipes%2Fsteps%2FUpload_to_test-results__telemetry_gpu_unittests_%2F0%2Fstdout Not 100% sure though. Some sample server logs: 06:15:08.532 Added data entry. :: {"id":4739537850073088, "index":0, "size":4026} 06:15:08.586 Read loading DataEntry ID: 5132870191677440 06:15:08.587 Read loading DataEntry ID: 4669997539655680 06:15:08.591 updateAggregate: merge :: {"error":"builder name conflict"} 06:15:08.591 updateAggregate: merge :: {"error":"builder name conflict"} 06:15:08.591 updateIncremental: inside transaction :: {"error":"builder name conflict"} 06:15:08.591 updateIncremental: inside transaction :: {"error":"builder name conflict"} 06:15:08.593 updateFullResults: updateIncremental :: {"error":"builder name conflict"} 06:15:08.593 uploadHandler :: {"error":"builder name conflict"}
,
Dec 13 2016
Those are errors on the client side, which is why we report 400. Also issue 673352 will make them log warning rather than an error.
,
Jan 18 2017
If this is really a Pri-1, find an owner and update the priority. This is the result of a bulk edit that moved high priority available bugs to a lower priority in an attempt to be more honest with bug filers.
,
Feb 16 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 13 2018
Very old. |
||||
►
Sign in to add a comment |
||||
Comment 1 by estaab@chromium.org
, Dec 13 2016