Bug 143109
| Summary: | CORE test continues even when SRPM not found | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Ready Certification Tests | Reporter: | Glen A. Foster <glen.foster> |
| Component: | other | Assignee: | Rob Landry <rlandry> |
| Status: | CLOSED WONTFIX | QA Contact: | Rob Landry <rlandry> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2 | CC: | hcp-admin, richardl, rick.hester |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | ia64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-04-14 17:46:42 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: | |||
|
Description
Glen A. Foster
2004-12-16 16:08:02 UTC
> I think it makes sense for the CORE test to stop-and-puke when SRPM is not found. It in fact does... > Cleaning scratch space (/tmp/rhr). > Checking/configuring environment... > CORE... > WARNING: SRPM not found ^^^ PUKE ^^^ > > WARNING: required space may not be available on /tmp/rhr > > Prep stage completed. > Press return to continue or control-c to quit ^^^ STOP ^^^ ...though perhaps that's puking then stopping :) It doesn't kill off the run since for some tests you could fix the above error at this point (eg. put a floppy into the drive) or perhaps you don't care about that specific test this time. Hrm. Well, the CORE test is pretty essential for every run. My advice (or preference) is to have the entire run *stop* since it's a fact that a missing SRPM value/file will invalidate the CORE test. It's the longest-running test (I think, I haven't made it all the way through the RHEL4 suite) and this is both a time-saver and a good check of dependencies. IMO, of course :) Certainly willing to consider it; though if the SRPM isn't found the test should be short. As well; if needed CORE can be run later, AFAIK there is no requirement for CORE with this NETWORK test. /me is looking for convincing to do the work ;) Since INFO seems to be run every time another test is executed, it might make more sense to have CORE abort the entire run so there's not much confusion. I'm thinking of the post-cert folks who will have to process all of this in addition to the overall 'usage model'. It's up to you. If it's not worth working on, close it WONTFIX and I won't be offended, but I wanted to offer the report/idea. FWIW. I'm going to go ahead and close this WONTFIX; the website will take partial results so a failed core doesn't invalidate the remaining of the tests. As well, ispec should copy the SRPMs for you. When in manual mode, one can <Ctrl>+<C> thier way out (either at the stopgap or during), so I think this is covered well enough. |