Bug 665272
| Summary: | Why so many tests lost their output? | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | QinXie <xiqin> | ||||||
| Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 5.3 | CC: | gasmith, hwcert-reviewers, rlandry, sdenham | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-04-06 19:53:25 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
QinXie
2010-12-23 05:45:05 UTC
This list is provided by wjw https://hardware.redhat.com/results.cgi?cert_id=661581&id=217336 https://hardware.redhat.com/results.cgi?cert_id=662535&id=217574 https://hardware.redhat.com/results.cgi?cert_id=662535&id=217594 https://hardware.redhat.com/results.cgi?cert_id=659587&id=218032 Created attachment 472669 [details]
rundocument.py patch to fail tests with missing logs
This patch changes v7 to detect missing logs, and mark the tests as FAIL. It also puts error messages errors reading the logs in the test log.
Created attachment 472670 [details]
hardwaretest.patch to detect log reading errors
I suspect this was originally reported in: https://bugzilla.redhat.com/show_bug.cgi?id=642505 https://bugzilla.redhat.com/show_bug.cgi?id=642144 ..but was linked to catalog rather than test suite. I suggest we can safely close those 2 BZs off as DUPs of this one. FJ are experiencing this a lot on their testing and I'm sure they'd be willing to run any debug options in order to try and track this down as they're finding it a frustration. Any suggestions on how to debug, ie, strace etc? |