fedora-ci.koji-build.tier0.functional fails due to "ERROR: Test
environment installation failed: reason unknown, please escalate"
by Adam Williamson
There's an update in Bodhi that's stuck right now because fedora-
ci.koji-build.tier0.functional failed for lorax, which has it
configured as a blocking test in its gating.yaml. This is the test:
https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pi...
the console output shows:
Waiting for Testing Farm...
[Pipeline] waitForWebhook
[Pipeline] retry
[Pipeline] {
[Pipeline] httpRequest
[Pipeline] }
[Pipeline] // retry
[Pipeline] echo
The status is now "running"
[Pipeline] echo
Waiting for Testing Farm...
[Pipeline] waitForWebhook
[Pipeline] retry
[Pipeline] {
[Pipeline] httpRequest
[Pipeline] }
[Pipeline] // retry
[Pipeline] echo
The status is now "error"
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Process Test Results (XUnit))
Stage "Process Test Results (XUnit)" skipped due to when conditional
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] catchError
[Pipeline] {
[Pipeline] error
[Pipeline] }
ERROR: Test environment installation failed: reason unknown, please escalate
Does anyone know what's going on there? I did retry the test, and it
failed the same way both times, so it doesn't seem like a blip.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net
2 years, 3 months
Why every CI we have must have so complex setup?
by Vít Ondruch
Hi everybody and sorry for the rant, but I must vent somewhere.
So I am preparing updated Ruby package. I know that there is rpminspect
executed at some point and the results are available in Bodhi [1].
Therefore, I'd like to execute similar test on my machine prior pushing
anything anywhere. So lets give rpminspect a shot:
~~~
$ rpminspect
rpminspect: Please specify a configuration file using '-c' or supply
./rpminspect.yaml
~~~
Hm, bummer. So how is this configured in Bodhi? Lets look at Jenkins
[2]. Hm, nice, but how is it executed? No clue.
So lets try the main task [3]. Ha, console [4], there must be the
"rpminspect" command, right? But no, there is non. There is just 11
pages of nonsense.
So looking once again, ok, kubernetes, there is used some container.
Lets check what the rpminspect-pipeline stands for, opening its
repository [5]. FMF, that sounds familiar, lets open the rpminspect.fmf
[6]. Hm, /usr/local/bin/rpminspect_runner.sh, what is that? How can I
get it? Ah, there is image repository and the file [7], which as again
more then 5 pages of gibberish. There finally some `rpminspect` call on
line 155 [8], but then I could continue with localization of the config
file.
This is really awful and I suffer every time I have to do something like
this. I am really frustrated. I really don't understand, why the command
can't be visible as far as at the console [4].
Comparing e.g. with GH actions, I have opened cpython repository for the
first time in my life and on 5 clicks, I know the test suite is executed
via `make buildbottest TESTOPTS="-j4 -uall,-cpu"`.
Do I want to try to test rpminspect at this moment? No, No, No and no
again, because this is not CI, this is just torture. This is so
intimidating.
So, would it be so big problem to have the several rpminspect calls
which are certainly done somewhere at some point visible on the Jenkins
console [4]?
/rant
Vít
P.S. Once again sorry and please no offense.
[1] https://bodhi.fedoraproject.org/updates/FEDORA-2021-62cd39359e
[2]
https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/rpminspect-...
[3]
https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/rpminspect-...
[4]
https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/rpminspect-...
[5] https://github.com/fedora-ci/rpminspect-pipeline
[6]
https://github.com/fedora-ci/rpminspect-image/blob/master/rpminspect_runn...
[7]
https://github.com/fedora-ci/rpminspect-pipeline/blob/master/rpminspect.fmf
[8]
https://github.com/fedora-ci/rpminspect-image/blob/master/rpminspect_runn...
2 years, 3 months
