| Summary: |
Create a test to look for most issues reports in logs |
| Product: |
[QA/Testing] Runtime Testing
|
Reporter: |
Stoicescu Cornel <corneliux.stoicescu> |
| Component: |
general | Assignee: |
Lucian Musat <georgex.l.musat> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
enhancement
|
|
|
| Priority: |
Medium
|
CC: |
alexandru.c.georgescu, alexandrux.palalau, bluelightning, ionutx.chisanovici, sstncr
|
| Version: |
1.6 | |
|
| Target Milestone: |
1.7 M3 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
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)