I think we disabled email notifications for bvt-perbuild as there was no active monitoring of auto-filed bugs and the filing frequency was very high.

We don't need auto-filed bugs. We only want the email notifications for bvt-perbuild. Is it OK to turn it on? Rohit. Who's the right owner for it?

I found control.bvt-perbuild has another bug template (#1).

According to #2, 
The settings in this bug template will be merged to the bug template defined in suite control file. That is, labels and cc defined in both test and suite control files will be merged and applied to the bug filed." It looks like the bug template in test control is not applied.

#1: https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/test_suites/control.bvt-perbuild?dr=C

#2: https://www.chromium.org/chromium-os/testing/test-suites

Add dshi and ayatane.

video_VideoDecodeAccelerator has a BUG_TEMPLATE that cc chromeos-video-test-failures@google.com. But we haven't received any emails. Do you know why?

https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/client/site_tests/video_VideoDecodeAccelerator/control.vp8?dr=C&l=24

Are you referring to the task:
[NightlyStormBvtPerBuild]
run_on: nightly
hour: 14
suite: bvt-perbuild
branch_specs: ==tot
boards: storm
pool: suites

It needs a "file_bugs: True" setting to enable bug filing

Re #3: AFAIK, Dan is the one :-)

Re 10: I don't need bug filing. I want to know why emails are not sent to cc list of video_VideoDecodeAccelerator.

By the way, I cannot find which source file contains the task [NightlyStormBvtPerBuild]. Which file is that?

I found an old email syaing "Recently we disabled the auto-filing bug feature for all suites except the tree-closing suites ('au', 'bvt-.*', 'paygen_.*', 'sanity'), all the other suites will default to just send email notifications to groups that developers had specified in the bug template when the tests fail."

This explained why video suite has file_bugs=True but it doesn't have auto-filed bugs. We still receive failure emails.

I found the suites that will file bugs.
_FILE_BUG_SUITES = ['au', 'bvt', 'bvt-cq', 'bvt-inline', 'paygen_au_beta',
                    'paygen_au_canary', 'paygen_au_dev', 'paygen_au_stable',
                    'sanity', 'push_to_prod']

https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/server/cros/dynamic_suite/suite.py?q=package:%5Echromeos_public$+%5C%27bvt-&l=44&dr=C

This means we can set file_bugs=True for bvt-perbuild. Theoretically we will receive failure emails and won't have auto-filing bugs. That's exactly what we need. But maybe we need to tell people before we merge the CL.

https://cs.corp.google.com/search/?q=package:chromeos_public+suite:bvt-perbuild+BUG_TEMPLATE+%22%27cc%27%22&type=cs

According to code-search except for video tests there are only two affected tests:
logging_CrashServices
'cc': ['vapier@chromium.org', 'benchan@chromium.org'],

autoupdate_CatchBadSignatures
'cc': ['chromeos-installer-alerts@google.com'],

We could tell them in advance.

https://chrome-internal-review.googlesource.com/c/332643/ is in review.

Re 16: Yes. Please notify them.

re #14
right, you need to add bvt-perbuild to that list.

re #18

Since what we expect is to receive failure mails and not auto-file bugs, I think what we need to do is to add "file_bugs: True" in NightlyStormBvtPerBuild (as CL below), not add bvt-perbuild to _FILE_BUG_SUITES list.

Is this correct?

https://chrome-internal-review.googlesource.com/c/332643/

Re #19
that's correct, no need to add the suite to that list.

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/624a8116b063a7e34db30a1bb0586a2bca53cb32

commit 624a8116b063a7e34db30a1bb0586a2bca53cb32
Author: Pin-chih Lin <johnylin@google.com>
Date: Thu Mar 02 10:45:31 2017

Dan. I don't see any test failure email yet for video_VideoDecodeAccelerator. Is there anything else to be done?

There is an example (we should receive failure mails in chromeos-video-test-failures@google.com but still no)

test:video_VideoDecodeAccelerator
platform:guado
build:R58-9332.0.0
https://wmatrix.googleplex.com/testrun/unfiltered?test_ids=442366635

Check suite log autoserv.DEBUG under this link
https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/104414300-chromeos-test/hostless/debug
03/02 15:30:48.875 INFO |        server_job:0184| END FAIL	104436633-chromeos-test/chromeos4-row3-rack8-host3/video_VideoDecodeAccelerator	video_VideoDecodeAccelerator	timestamp=1488497383	localtime=Mar 02 15:29:43
......
03/02 15:30:50.754 DEBUG|         gmail_lib:0120| Email sent: 15a915c9dcfd0747

"Email sent" should mean it had sent mails to someone else, but not chromeos-video-test-failures@google.com

And actually there is a mail in crosinfra2@gmail.com mailbox but the recipient is empty. (thanks for dshi@'s help)
---------------------------------------------------
From: <crosinfra2@gmail.com>
Date: Thu, Mar 2, 2017 at 3:30 PM
Subject: [bvt-perbuild] video_VideoDecodeAccelerator Failure on guado-release/R58-9332.0.0
To: 
---------------------------------------------------



Additional note: how to get suite log?
step1. Go to "details" page of failure test in Wmatrix
step2. Click "Job page"
step3. Click "parent job id", then click on "Debug logs" under "Hosts for this job"

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/chromeos-admin/+/67c222ff0b93a75d9bbacb4fe429a3b2602cfa7d

commit 67c222ff0b93a75d9bbacb4fe429a3b2602cfa7d
Author: Pin-chih Lin <johnylin@google.com>
Date: Thu Mar 09 04:50:30 2017