Issue #300: Testing Farm does not generate test-* repos for repository artifacts (Zuul) - general

fedora-ci / general

#300 Testing Farm does not generate test-* repos for repository artifacts (Zuul)

Closed Feb 23, 2022 by mvadkert. Opened Dec 1, 2021 by mvadkert.

For more context see:

https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org/thread/AOBM2MQ3LHDQIYCJ5GOHV6ZIYQK7TGJU/

Metadata Update from @mvadkert:
- Issue assigned to mvadkert

Dec 1, 2021

Metadata Update from @mvadkert:
- Issue assigned to guyinger (was: mvadkert)

Dec 1, 2021

churchyard commented Dec 10, 2021

See also https://pagure.io/fedora-ci/general/issue/167

churchyard commented Feb 22, 2022

Should we start opting-out of the rpm-sti-test job or at least mark it as non-voting in our affected packages? It has been almost 3 months and all our Zuul results are marked as failed, making it harder to spot real failures.

Edited Feb 22, 2022 by churchyard

fbo commented Feb 23, 2022

Hi @mvadkert do you think that could be addressed soon ? Having to make it non-voting would be like a step back on the road to only rely on testing farm for functional testing.

churchyard commented Feb 23, 2022

This also confuses casual contributors who go and investigate test failures when they don't need to: https://src.fedoraproject.org/rpms/python-tox/pull-request/85#comment-98272

mvadkert commented Feb 23, 2022

yeah sorry for the delay

mvadkert commented Feb 23, 2022

oh my, four lines for a workaround :dizzy_face:

testing: https://src.fedoraproject.org/rpms/python-tox/pull-request/86

mvadkert commented Feb 23, 2022

I believe the problem is resolved: https://src.fedoraproject.org/rpms/python-tox/pull-request/86

Metadata Update from @mvadkert:
- Issue status updated to: Closed (was: Open)

Feb 23, 2022

churchyard commented Mar 18, 2022

This indeed seems to be working as expected. Thank you!

mvadkert commented Mar 18, 2022