Issue metadata
Sign in to add a comment
|
[BVT-CQ: Winky & Celes] logging_UdevCrash test is failing with "Crash report contains invalid content .." |
||||||||||||||||||||||
Issue descriptionChrome Version: 10073.0.0 OS: ChromeOS Device: Winky Test: logging_UdevCrash wmatrix: https://wmatrix.googleplex.com/unfiltered?hide_missing=True&tests=logging_UdevCrash&releases=tot&platforms=winky,celes&days_back=30 Failure Reason: "Crash report contains invalid content ['2017-11-08T06:25:55.812108-08:00 DEBUG kernel: [ 0.466159] acpi ATML0000:00: GPIO: looking up atmel,reset-gpios', '2017-11-08T06:25:55.812115-08:00 DEBUG kernel: [ 0.466165] acpi ATML0000:00: GPIO: looking up atmel,reset-gpio', '2017-11-08T06:25:55.814555-08:00 DEBUG kernel: [ 0.479167] acpi ATML0000:01: GPIO: looking up atmel,reset-gpios', '2017-11-08T06:25:55.814566-08:00 DEBUG kernel: [ 0.479188] acpi ATML0000:01: GPIO: looking up atmel,reset-gpio']" Job link: https://wmatrix.googleplex.com/testrun/unfiltered?test_ids=594501682 This is a regression from M64 build 10073.0.0 https://screenshot.googleplex.com/isk2goPKaNu Noticed same failure on celes, but not consistent.
,
Dec 12 2017
failed on caroline chrome-pfq-informational today: https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/caroline-tot-chrome-pfq-informational/builds/524
,
Jan 15 2018
,
Jan 18 2018
logging_UdevCrash test is failing on Winky and Celes on today's beta build M64-BETA-CHROMEOS-7 (10176.54.0, 64.0.3282.101)
,
Feb 7 2018
This is still failing on winky R65-10323.21.0
,
Feb 13 2018
logging_UdevCrash test is failing on Winky and Celes on beta build M65-BETA-CHROMEOS-1 (10323.30.0, 65.0.3325.65).
,
Mar 1 2018
Celes job link: https://ubercautotest.corp.google.com/afe/#tab_id=view_job&object_id=180198697 Failure: Crash report contains invalid content ['2018-03-01T01:43:32.999353-08:00 DEBUG kernel: [ 0.812195] acpi ATML0000:01: GPIO: looking up atmel,reset-gpios', '2018-03-01T01:43:32.999357-08:00 DEBUG kernel: [ 0.812201] acpi ATML0000:01: GPIO: looking up atmel,reset-gpio']
,
Mar 19 2018
This is still happening on the 65 stable build for celes. It also happened for Winky but eventually passed. Do we have a good owner for this?
,
Mar 19 2018
i don't think people need to keep listing specific versions/branches/boards. it's known to be broken for a bunch of boards starting in M64. needs someone on the touchpad team to look into it, but i don't know who that'd be (beyond adlr@).
,
Mar 28 2018
This is still happening on the 66 beta build for winky (Chrome OS version: 10452.30.0, 66.0.3359.67)
,
Mar 29 2018
Issue 827232 has been merged into this issue.
,
Apr 4 2018
adlr@, can you help triage this? This has been showing up consistently on winky and celes and it means every release we do has these flagged and it causes churn with the test and release teams.
,
Apr 30 2018
happening in caroline today, see the builder here https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8947814833441549360
,
May 4 2018
Any update on an owner for this? We continue to see this failure on 68.
,
May 4 2018
Looks like the issue is that https://chromium.googlesource.com/chromiumos/platform2/+/master/crash-reporter/crash_reporter_logs.conf says you collect kernel logs with the keyword "atmel" , but in the autotest we require the keyword 'atmel_mxt_ts'. I'll post a change to crash_reporter_logs.conf to use the same keyword as the test
,
May 4 2018
https://chromium-review.googlesource.com/c/chromiumos/platform2/+/1045143 I put derat@ to review, but if anyone wants to review while he's ooo then go for it.
,
May 12 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform2/+/8d8f6387461e39b651227355444b7d2c15c59b42 commit 8d8f6387461e39b651227355444b7d2c15c59b42 Author: Andrew de los Reyes <adlr@chromium.org> Date: Sat May 12 00:55:19 2018 crash: crash_reporter_logs.conf: Fix keyword for Atmel This keyword should match the keyword in logging_UdevCrash BUG= chromium:782857 TEST=None Change-Id: Idabc67f0e7588942975fe18333238ea66dd21be9 Reviewed-on: https://chromium-review.googlesource.com/1045143 Commit-Ready: Andrew de los Reyes <adlr@chromium.org> Tested-by: Andrew de los Reyes <adlr@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> [modify] https://crrev.com/8d8f6387461e39b651227355444b7d2c15c59b42/crash-reporter/crash_reporter_logs.conf
,
May 14 2018
should be safe to merge back. guessing TPMs only want to do M66.
,
Jun 7 2018
,
Aug 17
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by vapier@chromium.org
, Nov 8 2017Owner: adlr@chromium.org