[tools] Checksum/size comparison of autoinst.xml FAILED
https://openqa.suse.de/tests/975720 fails as incomplete. Everything inside the autoinst-log.txt looks fine except this line:
+++ worker notes +++
end time: 2017-06-01 22:48:25
Checksum comparison (actual:expected) 4294967295:1179459072 with size (actual:expected) 0:51985
Checksum/size comparison of autoinst.xml FAILED
First occasion I saw with this error and I'm not 100% certain if the failed log is really the reason for the incomplete failure.
Also a hard failure (with incomplete) just because of missing logs/assets seems exaggerated to me. Maybe an additional notice (which would have to be introduced) about failing "post test handling" makes such problems more obvious than a incomplete test - but that is just an idea of mine.
#4 Updated by nicksinger over 4 years ago
Hm… Now that you said it this seems to be the most likely cause of this.
But what I then cannot explain is, why this succeeds (EXIT 0 means successful to me):
22:40:42.7744 18211 running nice ionice qemu-img convert -O qcow2 raid/l1 assets_public/SLES-12-SP3-ppc64le-Build0409-gnome.qcow2 -c
18211: EXIT 0
while the only problem is with autoinst.xml.
IMHO we need better logging here.
#8 Updated by okurz over 4 years ago
sle-12-SP3-Server-DVD-x86_64-Build0410-sles12_textmode_create_hdd@64bit is another one. Ok, definitely not ppc64le tmpfs related :-)
#11 Updated by szarate over 4 years ago
- Assignee deleted (
- Target version deleted (
It might be that somehow the chksum call is timing out due to nfs being too busy or so... But that's just a theory after talking to coolo when I came across this problem with the seattles (that basically had no nfs mount, and the checksums were failing all the time).
I guess splitting the checksum and removing the dependency with nfs (except from the repos), could be a wise thing to do.
Also, removing the milestone.