Hello Adam,
seem there is a timing window problem between Rawhide tests and f32
release as per failure https://openqa.fedoraproject.org/tests/587422
===
Cannot find HDD_1 asset hdd/disk_f32_support_5_x86_64.img!
===
failed Fedora-Rawhide-20200426.n.1 about an hour ago ( 0 )
failed Fedora-Rawhide-20200425.n.0 2 days ago ( 0 )
passed Fedora-Rawhide-20200423.n.0 4 days ago ( 02:00 minutes )
===
There is not yet a f32 in
https://fr2.rpmfind.net/linux/fedora/linux/releases/
===
[DIR] 30/ 2019-04-26 22:58 -
[DIR] 31/ 2019-10-25 17:05 -
[DIR] test/ 2020-03-13 21:00 -
===
I experienced similar problem trying createhdds for ppc64le
--
Michel Normand
Hello Adam,
I identified two tests that randomly failed on
openqa.stg.fedoraproject.org (1)&(2)
We do not have such problem in our IBM intranet openQA.
So I am wondering if difference could be related to
configuration/software versions differences of P9 hosts.
Our P9 is installed with f31, but no updates since 03/17
===
$rpm -qa |grep -iE ^'kernel-header|qemu-kvm|slof' |sort
kernel-headers-5.5.8-200.fc31.ppc64le
qemu-kvm-4.1.1-1.fc31.ppc64le
SLOF-0.1.git20191022-1.fc31.noarch
===
From last autoinst-log.txt and serial0.txt it seems you have same slof
older kernel and specific qemu.
Do you have other specific changes ?
===
Linux 5.3.16-300.fc31.ppc64le
qemu-4.2.0-1.fc31.infra
SLOF release 20191022
===
(1) server flavor install_default_upload, failed only one time (last
compose 20200402)
https://openqa.stg.fedoraproject.org/tests/794105#step/_console_wait_login/8
(2) server flavor upgrade_2_minimal, failed multiple times
https://openqa.stg.fedoraproject.org/tests/794304#step/_console_wait_login/…https://openqa.stg.fedoraproject.org/tests/794304#next_previous
--
Michel Normand
I'm working on something that looks for certain results in resultsdb
and I'm getting some strange results. I'm hoping someone here can point
out what I'm doing wrong.
I'm hitting an issue where the data I'm getting back from resultsdb via
the api isn't matching what I see in the frontend. The result is
clearly in the db (I can get the data if I query the result ID) but
when I search for the result using one of its keywords, I get an empty
set back. What's even stranger is that this isn't consistent - some
results submitted around the same time return the results I expect.
I wrote up a quick script to show what I'm seeing:
https://gist.github.com/tflink/1a1ed4263fbeb56b04442a948770965f
It includes the output I'm seeing at the moment as I suspect it'll
start working as soon as someone else looks at it :)
I've tried this on the resultsdb production machine and I'm seeing the
same results. I feel like I'm missing something obvious here so if you
see it, I'd appreciate the help.
Thanks,
Tim
