Actions
action #18314
closed[tools] libpng error: Write Error
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Regressions/Crashes
Target version:
-
Start date:
2017-04-04
Due date:
% Done:
0%
Estimated time:
Description
observation¶
The testcase https://openqa.suse.de/tests/833472 shows the error "libpng error: Write Error" two times in its logs.
The format of the message is not the default log message format and also the job keeps running like if nothing happened.
steps to reproduce¶
No clue how to reproduce this.
problem¶
The error does not provide any information how critical it is. Also it seems like it bypasses the default log facility making it even harder to judge.
suggestion¶
Catch the error and provide a message with the proper importance for the user over the default log facility.
If this error is critical, a defined exit of the test should be considered too.
Actions