fedora-infra
GNU backend - use ftpmirror
Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci https://fedora.softwarefactory-project.io/zuul/buildset/ff8c0c7c9da24302bcc4461ec2df60a6
:heavy_check_mark: fi-tox-mypy SUCCESS in 5m 53s :heavy_check_mark: fi-tox-lint SUCCESS in 4m 42s :heavy_check_mark: fi-tox-format SUCCESS in 5m 38s :x: fi-tox-python310 FAILURE in 8m 25s :x: fi-tox-python311 FAILURE in 7m 43s :x: fi-tox-python312 FAILURE in 9m 03s :heavy_check_mark: fi-tox-docs SUCCESS in 6m 06s :heavy_check_mark: fi-tox-bandit SUCCESS in 4m 40s :x: fi-tox-diff-cover FAILURE in 9m 49s
![softwarefactory-project-zuul[bot] avatar](https://avatars.githubusercontent.com/in/6924?v=4 "Published by a pub.dev verified publisher"){kind=small}
I have no idea how to write tests, but I am happy to add something to the News file.
I have no idea how to write tests, but I am happy to add something to the News file.
Just look at the failing tests and how they are written, I assume it's just changing the url that is being accessed in the tests.
I have no idea how to write tests, but I am happy to add something to the News file.
Just look at the failing tests and how they are written, I assume it's just changing the url that is being accessed in the tests.
As a long-time Ghostbusters aficionado, my understanding of how to handle Zuul complaining is to just lie to it.
Having said that, these Zuul test failures seem quite opaque, and a simple PR like this tripping them indicates a configuration issue either upstream or somewhere else, no?
I also can't make heads or tails of what to do to try to fix the errors looking at https://fedora.softwarefactory-project.io/zuul/buildset/ff8c0c7c9da24302bcc4461ec2df60a6 . There are no logs to see there by default...
@satmandu The logs in zuul are kept only for few days, this explains why the logs aren't there anymore. Doing another run should show the errors. Even running the tests locally should show you what is failing.
The reason why they don't pass is that there is change in code and no change in tests. So they just don't get the correct output for the change. This is how unit tests should work. So failing is correct in this case.