No mail notification for suite:crosbolt_perf_nightly tests |
|||||||
Issue descriptionWe've found that chromeos-video-test-failures@ didn't get any mail notification which we should for suite:crosbolt_perf_nightly tests, e.g. video_VideoVDAPerf. control file: https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/site_tests/video_VDAPerf/control.h264?dr=C There is cc to chromeos-video-test-failures@ suite_scheduler.ini: (file_bugs=True) # Please do not add tests to this suite without first clearing it with the # crosbolt team. [CrosboltArcPerfNightly] run_on: nightly hour: 16 suite: crosbolt_arc_perf_nightly branch_specs: >=tot-1 pool: crosperf file_bugs: True And on WMatrix there are several failures: https://wmatrix.googleplex.com/unfiltered?hide_missing=True&days_back=30&releases=59&tests=video_VDAPerf&suites=crosbolt_perf_nightly Is there any cause blocking the notification? Thanks
,
Mar 17 2017
Thanks a lot
,
Mar 17 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/c53d4d9d5de85630ee1e930d09f7a6fc1f67f5ee commit c53d4d9d5de85630ee1e930d09f7a6fc1f67f5ee Author: Pin-chih Lin <johnylin@google.com> Date: Fri Mar 17 13:49:18 2017 Enable file_bugs of suite crosbolt_perf_nightly There are several video tests we'd like to monitor in crosbolt_perf_nightly suite. We'd like to enable file_nugs. BUG= chromium:702509 TEST=None Change-Id: I37c58b22c43816141674bde1b9492e51f175fcda Reviewed-on: https://chromium-review.googlesource.com/456978 Commit-Ready: Pin-chih Lin <johnylin@chromium.org> Tested-by: Pin-chih Lin <johnylin@chromium.org> Reviewed-by: Dan Shi <dshi@google.com> [modify] https://crrev.com/c53d4d9d5de85630ee1e930d09f7a6fc1f67f5ee/test_suites/control.crosbolt_perf_nightly
,
Mar 18 2017
,
Mar 18 2017
I think Ben's team is watching for performance regressions. Ben, could someone from your team change TO and CC in the suite file?
,
Mar 22 2017
,
Jul 17 2017
ChromeOS Infra P1 Bugscrub. P1 Bugs in this component should be important enough to get weekly status updates. Is this already fixed? -> Fixed Is this no longer relevant? -> Archived or WontFix Is this not a P1, based on go/chromeos-infra-bug-slo rubric? -> lower priority. Is this a Feature Request rather than a bug? Type -> Feature Is this missing important information or scope needed to decide how to proceed? -> Ask question on bug, possibly reassign. Does this bug have the wrong owner? -> reassign. Bugs that remain in this state next week will be downgraded to P2.
,
Jul 24 2017
ChromeOS Infra P1 Bugscrub. Issue untouched in a week after previous message. Downgrading to P2.
,
Jun 8 2018
Hi, this bug has not been updated recently. Please acknowledge the bug and provide status within two weeks (6/22/2018), or the bug will be closed. Thank you.
,
Jun 11 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by dshi@chromium.org
, Mar 17 2017Owner: johnylin@chromium.org