action #18314
closed[tools] libpng error: Write Error
0%
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.
Updated by okurz almost 8 years ago
- Related to action #17986: [sles][functional] test fails to switch to details view in start_install added
Updated by nicksinger almost 8 years ago
- Subject changed from libpng error: Write Error to [tools] libpng error: Write Error
Updated by coolo almost 8 years ago
- Status changed from New to Rejected
this is a symtom of the caching not done yet correctly. We added some workaround
Updated by mgriessmeier almost 8 years ago
this is back on malbec:
https://openqa.suse.de/tests/883441#step/start_install/7
Updated by mgriessmeier almost 8 years ago
- Status changed from Rejected to In Progress
Updated by mgriessmeier almost 8 years ago
- Status changed from In Progress to Resolved
as discussed with richard
relating to https://progress.opensuse.org/issues/18632