Fix test scripts for non-ERROR Failures
Bug #1605649 reported by
Robert P. Goldman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ASDF |
Fix Released
|
Undecided
|
Robert P. Goldman | ||
Bug Description
ECL can raise some SERIOUS-CONDITIONs that are not ERRORs but that would constitute a test failure. These are mostly for various flavors of resource exhaustion.
See the ECL bug I filed here: https:/
Need to examine the script-support code and appropriately catch SERIOUS-CONDITION as well as ERROR, at least on ECL.
Revision history for this message
| Robert P. Goldman (rpgoldman) wrote | #1 |
| summary: |
- Fix test scripts for ECL non-ERRORs + Fix test scripts for non-ERROR Failures |
Revision history for this message
| Robert P. Goldman (rpgoldman) wrote | #2 |
| Changed in asdf: | |
| status: | New → Fix Committed |
| assignee: | nobody → Robert P. Goldman (rpgoldman) |
| Changed in asdf: | |
| status: | Fix Committed → Fix Released |
| milestone: | none → 3.3 |
To post a comment you must log in.
OK, this is not an ECL-specific problem, it's just that I never encountered it on other lisps. In fact, STORAGE-CONDITION is generally a class of SERIOUS-CONDITION that's not an ERROR, that our test scripts should catch.
Another reason why this is particularly important on ECL is that on some other lisps we have a mode of operation that disables the debugger and exits with error rather than dropping into the REPL. I don't believe there is such a mode for ECL. If so, I haven't found it.