Dashboard: implement quarantine for bad reports |
||
Issue descriptionThat would allow cron to recover from most of the errors. E.g. if a report with low coverage was uploaded, right now we'll report an error and that will need some manual work to investigate + unblock further reports to be published. Manual work for investigation is not avoidable, which is fine, but we can move "bad" report to a separate quarantine directory in order to let further reports to be automatically processed and published if they are good.
,
Jun 2 2018
Just tested https://chrome-internal-review.googlesource.com/c/chrome/tools/code-coverage/+/634743 on prod, works fine. No need to do any manual clean up over the weekend, bad reports should be automatically moved to the quarantine with errors reported, valid reports will be published as they should be.
,
Jun 2 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/tools/code-coverage/+/8b94b07376706b03a4518689088ec74d9f287b5d commit 8b94b07376706b03a4518689088ec74d9f287b5d Author: Max Moroz <mmoroz@google.com> Date: Sat Jun 02 04:34:03 2018
,
Jun 4 2018
The following revision refers to this bug: https://chrome-internal.googlesource.com/chrome/tools/code-coverage/+/5d41915709c43dcce82a276f37dd16545a8bd746 commit 5d41915709c43dcce82a276f37dd16545a8bd746 Author: Max Moroz <mmoroz@google.com> Date: Mon Jun 04 06:04:53 2018 |
||
►
Sign in to add a comment |
||
Comment 1 by mmoroz@chromium.org
, Jun 2 2018Status: Started (was: Untriaged)