Our CI test does this:
original="/etc/mock/fedora-${fedora}-x86_64.cfg" cp $original $config echo -e '\n\nconfig_opts[f"{config_opts.package_manager}.conf"] += """' >> $config # The zuul CI has zuul-build.repo # The Jenkins CI has test-<pkgname>.repo # We run this code from various packages, so we support any <pkgname> if [ -f /etc/yum.repos.d/zuul-build.repo ]; then cat /etc/yum.repos.d/zuul-build.repo >> $config else cat /etc/yum.repos.d/test-*.repo >> $config fi echo -e '\n"""\n' >> $config
https://src.fedoraproject.org/rpms/pyproject-rpm-macros/blob/master/f/tests/mocktest.sh
It broke recently on jenkins, with:
+ cat '/etc/yum.repos.d/test-*.repo' cat: '/etc/yum.repos.d/test-*.repo': No such file or directory
https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pipeline/job/master/2243/testReport/(root)/tests/pyproject_pytest/
Has the repo file path been changed recently?
Thanks for reporting, seems to be same as #165, the new system does not yet create repositories, but it should. Will keep the name as you expect it.
Metadata Update from @msrb: - Issue tagged with: STI-compat, Testing Farm, bug
I believe this is now fixed, repo test-artifacts should be now added.
test-artifacts
http://artifacts.dev.testing-farm.io/e64e5a52-8297-4d1e-8871-23dbcf5a560d/guest-setup-e18110ca-9acd-4f8e-8dcb-d1877ea7258c/guest-setup-output-post-artifact-installation.txt
Trying to rerun this testin
Testing here: https://osci-jenkins-1.ci.fedoraproject.org/job/fedora-ci/job/dist-git-pipeline/job/master/260/console
Seems to be doing something according to logs: Test artifacts repository 2.9 MB/s | 3.0 kB 00:00
...
@churchyard can you confirm this is now ok for you pls?
Doing so in https://src.fedoraproject.org/rpms/python-toml/pull-request/8
looks good, closing. Thanks for confirming @churchyard
Metadata Update from @mvadkert: - Issue status updated to: Closed (was: Open)
Thanks for the fix.