Project

General

Profile

Actions

action #12230

closed

libpng error: Read Error

Added by okurz almost 8 years ago. Updated almost 8 years ago.

Status:
Rejected
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
2016-06-04
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

observation

See https://openqa.suse.de/tests/411001 on ppc64le

libpng error: Read Error
Could not open image qemuscreenshot/shot-0000001328.png
libpng error: Read Error
Could not open image qemuscreenshot/shot-0000001328.png
test install_and_reboot died at /usr/lib/os-autoinst/basetest.pm line 293.
21:03:59.9026 <<< check_screen(mustmatch=[
  'yast-still-running',
  'linuxrc-install-fail',
  'linuxrc-repo-not-found'
], timeout=5)
21:03:59.9708 MATCH(yast-still-running-20140204:0.98)
21:04:00.0345 MATCH(yast-still-running-20140728:0.98)
21:04:00.1683 MATCH(yast-still-running-B-20131217:0.00)
21:04:00.2514 MATCH(yast-still-running-20131217:0.00)
21:04:00.3350 MATCH(yast-still-running-text-20150508:0.00)
21:04:00.4136 MATCH(yast-still-running-20160429:1.00)
21:04:00.5087 MATCH(yast-still-running-20160509:1.00)
21:04:00.5716 MATCH(linuxrc-install-fail-20140624:0.00)
libpng error: Read Error
Could not open image qemuscreenshot/shot-0000001328.png
21:04:00.5827 post_fail_hook failed: Can't call method "write_with_thumbnail" on an undefined value at /usr/lib/os-autoinst/basetest.pm line 151.
Actions #1

Updated by okurz almost 8 years ago

  • Description updated (diff)
  • Priority changed from Urgent to High

yeah, ok. maybe it's just the one test

Actions #2

Updated by coolo almost 8 years ago

  • Status changed from New to Rejected

this happens if you overuse the pool directory - it's a risk we take open eyed. Normally the disks are not full and as such the qcows fit. But with bad luck all qcows get full at the same time. Just track all such issues in this issue - and once we cross a critical mass, we might want to do something about it. For now -> retrigger

Actions #3

Updated by okurz almost 8 years ago

should we automatically retrigger and spat out a warning in this case? Or more specifically: How can we regard this as incomplete so that it is automatically retriggered?

Actions #4

Updated by coolo almost 8 years ago

If we have to do this more than once a day, I'd say so.

Actions

Also available in: Atom PDF