Closed Bug 369859 Opened 18 years ago Closed 17 years ago

reftest should continue if a file in the manifest is not found

Categories

(Core :: Layout, defect)

Product:
Core
Component:
Layout
Platform:
PowerPC
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: rcampbell, Unassigned)

Details

Current behaviour is to display the "not found" error page and halt execution. Instead of this, reftest should report the error to the logs (marking the tests as failed) and continue executing.
Looking at the current reftest code, I don't think this actually happens any more, except that if you try to include a non-existent file, it'll cause reftest to abort with a failure message. Does the original problem still happen, and if not, can we close this? I don't really think it's worth caring about the not-found include, and if that's all this bug maybe-covers, I think we should close it.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.