5747 2014-01-21 14:30:12 +0000 Create a test to look for most issues reports in logs 2014-09-09 11:00:37 +0000 1 1 10 QA/Testing Runtime Testing general 1.6 x86 Multiple RESOLVED FIXED Medium enhancement 1.7 M3 1 corneliux.stoicescu georgex.l.musat alexandru.c.georgescu alexandrux.palalau bluelightning ionutx.chisanovici sstncr --- --- No (bug/feature does not impact docs) oldest_to_newest 39964 0 corneliux.stoicescu 2014-01-21 14:30:12 +0000 Currently all we have is a test that looks for the "error" keyword in dmesg output. We should have better regex pattern to use on all existing logs on the image. This requires: - a well thought out regex pattern to identify issues lile: "error", "cannot", "can't", "failed" * these regex patterns should NOT be key sensitive - a list of places to look for logs and/or exact log locations. - As many logs as possible should be enabled on tested images (kern.log can only be found on lsb images) This should work really well with automated runtime testing(both qemu and BSP) 42876 1 alexandru.c.georgescu 2014-04-23 08:24:02 +0000 moving to 1.7 44230 2 alexandru.c.georgescu 2014-06-30 06:58:55 +0000 Moved to M2. 45488 3 georgex.l.musat 2014-09-09 10:59:48 +0000 Ptest runtime test has been developed and it's waiting review 45489 4 georgex.l.musat 2014-09-09 11:00:37 +0000 Disregard previous comment. The error log parser has been developed and merged. Closing this.