Bug 5747 - Create a test to look for most issues reports in logs
Summary: Create a test to look for most issues reports in logs
Status: RESOLVED FIXED
Alias: None
Product: Runtime Testing
Classification: QA/Testing
Component: general (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 1.7 M3
Assignee: Lucian Musat
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-01-21 14:30 UTC by Stoicescu Cornel
Modified: 2014-09-09 11:00 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stoicescu Cornel 2014-01-21 14:30:12 UTC 
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)
Comment 1 Alexandru Georgescu 2014-04-23 08:24:02 UTC 
moving to 1.7
Comment 2 Alexandru Georgescu 2014-06-30 06:58:55 UTC 
Moved to M2.
Comment 3 Lucian Musat 2014-09-09 10:59:48 UTC 
Ptest runtime test has been developed and it's waiting review
Comment 4 Lucian Musat 2014-09-09 11:00:37 UTC 
Disregard previous comment. The error log parser has been developed and merged. Closing this.