-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin/builder: increase retries for requests to composer #128
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm slightly worried about these testcases that have started failing in this PR so I'll need to look deeper than just ack'ing this.
The fedora koji instance often has trouble contacting the composer api, let's just make the retries a lot more generous.
Note: codespell was removed here due to it's inability to handle CamelCase and the came case in question is from the external unittest library (which we won't change 😉 ) sidenode: an other option might be to disable checking of function names of external libraries, but also there doesn't seem to be support in codespell for this either |
The code changes are OK but shenanigans are going on with CI (CodeCov, Schutzbot). |
Koji complains if the `repo` isn't present.
This check is failing on the spelling of the valid function `assertIn` of the unittest library.
This package is no longer shipped.
Ok I think I got everything now, f41 didn't work because we're not building/testing f41 in composer yet, and koji-osbuild depends on osbuild-composer-tests. |
b01ac2a
to
f512d59
Compare
Drop the package sets, I'm not sure they exist anymore in that form, it breaks depsolving. Also pirnt the journal logs during the test to make it easier to debug failures.
The fedora koji instance often has trouble contacting the composer api, let's just make the retries a lot more generous.