New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 697742 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

bvt-cq tests didn't merge bug_template and cc the specified users

Project Member Reported by johnylin@chromium.org, Mar 2 2017

Issue description

We found that for suite:bvt-cq autotests we do have bug template as follows:

https://cs.corp.google.com/aosp-master/external/autotest/client/site_tests/video_ChromeHWDecodeUsed/control.h264?dr
BUG_TEMPLATE = {
    'labels': ['OS-Chrome', 'VideoTestFailure'],
    'cc': ['chromeos-video-test-failures@google.com'],
}

What we expect is the auto-filed bug of this test will have labels and cc to chromeos-video-test-failures@google.com. However, it didn't seem to merge BUG_TEMPLATE we specified.
Auto-filed bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=697312

Is there any problem on setting BUG_TEMPLATE or merging them?
 
Components: -OS>Kernel>Video
Ping?
we've found bvt-perbuild also have the similar issue, maybe it is a general bug.
Cc: akes...@chromium.org
Status: WontFix (was: Untriaged)
auto-filer is not actively supported, and likely to be deprecated entirely eventually. Please don't rely on it.
Status: Untriaged (was: WontFix)
Does "auto-filer is not actively supported" mean for both "auto-file bug" and "mail notification"?
Because right now our question is we didn't receive mail notification on bvt-cq failures which we should be in the cc list.

Thanks
Re #4: we don't care about auto-filed bugs. We just need cc of BUG_TEMPLATE of individual autotest to work so we can receive failure emails.
Owner: dshi@chromium.org
Ah, I meant specifically the auto-filer. Though I also don't know where the mail notifications are generated. dshi do you?

Comment 8 by dshi@chromium.org, Mar 7 2017

Bug filing and email is done in suite.py:
https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/server/cros/dynamic_suite/suite.py?rcl=b9d7adf07aec05db6a3f1a8b74f45abd7a87c74a&l=1059

The problem is not in autotest, it's the test suite's control file's bug template is mal-formatted:
https://chromium-review.googlesource.com/#/c/451546/
Project Member

Comment 9 by bugdroid1@chromium.org, Mar 8 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/efd85d631cc5745193a1b6d96fe3d0a8d48a289c

commit efd85d631cc5745193a1b6d96fe3d0a8d48a289c
Author: Dan Shi <dshi@google.com>
Date: Wed Mar 08 07:53:42 2017

[autotest] Fix bug template in suite control files

ccs is invalid, it should be cc.

BUG= chromium:697742 
TEST=None

Change-Id: I2620b0e1f618627e7067622010cced872b3bb674
Reviewed-on: https://chromium-review.googlesource.com/451546
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Ningning Xia <nxia@chromium.org>

[modify] https://crrev.com/efd85d631cc5745193a1b6d96fe3d0a8d48a289c/test_suites/control.push_to_prod
[modify] https://crrev.com/efd85d631cc5745193a1b6d96fe3d0a8d48a289c/test_suites/control.toolchain-tests
[modify] https://crrev.com/efd85d631cc5745193a1b6d96fe3d0a8d48a289c/test_suites/control.bvt-cq
[modify] https://crrev.com/efd85d631cc5745193a1b6d96fe3d0a8d48a289c/test_suites/control.perf_v2
[modify] https://crrev.com/efd85d631cc5745193a1b6d96fe3d0a8d48a289c/test_suites/control.bvt-inline
[modify] https://crrev.com/efd85d631cc5745193a1b6d96fe3d0a8d48a289c/test_suites/control.crosbolt_perf_nightly
[modify] https://crrev.com/efd85d631cc5745193a1b6d96fe3d0a8d48a289c/test_suites/control.crosbolt_perf_perbuild
[modify] https://crrev.com/efd85d631cc5745193a1b6d96fe3d0a8d48a289c/test_suites/control.test_that_wrapper
[modify] https://crrev.com/efd85d631cc5745193a1b6d96fe3d0a8d48a289c/test_suites/control.bvt-perbuild

Status: Assigned (was: Untriaged)
I still don't see any failure email to chromeos-lab-errors@ or chromeos-video-test-failures@. I checked the emails in chromeos-lab-errors group.

According to external/autotest/test_suites/control.bvt-perbuild, all failure emails in bvt-perbuild should go to chromeos-lab-errors@. 

Correction. We received some failure emails of bvt-perbuild tests in chromeos-video-test-failures@.
Status: Fixed (was: Assigned)
We received emails of bvt-perbuild tests. This is fixed.

Sign in to add a comment