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
ostree: Drop #9784
ostree: Drop #9784
Conversation
Priority as this at least needs to be considered for the next release, depending on the fedora 28 progress. |
fedora 28 dist-git branch now exists, package built and submitted to bodhi: https://bodhi.fedoraproject.org/updates/FEDORA-2018-0effffd2d7 |
Semapore fails with
I cannot reproduce that locally, there it works for me. But I think this is during distcheck, so apparently still something wonky there. Update: |
I cannot reproduce this in a container either, also not locally with a separate build tree:
This works fine. But I still have trouble to see in the log what actually failed, as there's no actual output from pyflakes, and this PR doesn't touch this part at all. The only error message that I see is
and indeed I don't see that in other semaphore runs. This smells like a weird race condition which has been there for a long time? |
I have an idea what's going on. test/avocado/testvm.py is a dangling symlink in the release tarballs, as they point to ../bots/ which we don't ship (by intent). So the question is rather, how can test-static-code and pyflakes sometimes do work in distcheck -- either it should always fail on the dangling symlink, or never. |
Oooooh, I know! Running pyflakes without the
So that error message just sometimes gets hidden because it interleaves with the pyflakes errors. But sometimes, if it is on a different line, we catch it. |
I sent PR #9789 to fix the flaky semaphore test, marking blocked as this needs to land after that to quiesce semaphore. |
This moved into a separate project: https://github.com/cockpit-project/cockpit-ostree Closes cockpit-project#9784
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.
This looks good (and satisfying).
One question though: I grepped through the commit and there's a bunch of references to the ostree package in the po files. Will these get removed or are the po files just identical across all cockpit-independent?
@Gundersanne: Indeed these are cruft now, but the next bot po-refresh will clean them up. I already imported the translations into cockpit-ostree, so they aren't lost either. |
This moved into a separate project:
https://github.com/cockpit-project/cockpit-ostree
As the standalone cockpit-ostree 175-1 is in Fedora rawhide now, the next release of Cockpit should not ship that any more, to avoid version conflicts and duplicate builds. I will also upload the standalone one to Fedora 28 as soon as the dist-git branch is created.