-
Notifications
You must be signed in to change notification settings - Fork 8
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
Invalidate old testing-farm request IDs and split up chroot comments #380
Conversation
Consider the chroot fedora-38-x86_64 only having successful builds. What happens is, that we kick of testing farm. But then you think that you need to change something and you kick of a new build in the fedora-38-x86_64 chroot again and it succeeds. In that case the testing-farm output will stay which is wrong by design. I not only need to log the chroot and request ID of testing farm but I need to log the old build IDs with it in order to properly invalidate any testing-farm output. |
chroot: str | ||
"""The chroot for which this testing-farm request was issues""" | ||
|
||
copr_build_ids: list[int] |
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.
Consider the chroot fedora-38-x86_64 only having successful builds. What happens is, that we kick of testing farm. But then you think that you need to change something and you kick of a new build in the fedora-38-x86_64 chroot again and it succeeds. In that case the testing-farm output will stay which is wrong by design. I not only need to log the chroot and request ID of testing farm but I need to log the old build IDs with it in order to properly invalidate any testing-farm output.
The Copr build IDs are now associated with a TestingFarmRequest
object.
The string `"artifacts.osci.redhat.com` may be at an arbitrary position in the sanitized URL. Resolve: #380 (review)
2512c56
to
68233d2
Compare
26b8e4d
to
a02574d
Compare
* splitting errors into their own distinct comments * links from the build matrix to the error comments * and more fixes
We use this in order to hide chroot comments for which no errors show up, hence they are outdated.
The string `"artifacts.osci.redhat.com` may be at an arbitrary position in the sanitized URL. See https://github.com/fedora-llvm-team/llvm-snapshots/security/code-scanning/2
4237837
to
dc75756
Compare
``` snapshot_manager/tests/github_util_test.py:69: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ self = <github.PaginatedList.PaginatedList object at 0x7f60c5d27e00>, index = 0 def __getitem__(self, index: Union[int, slice]) -> Any: assert isinstance(index, (int, slice)) if isinstance(index, int): self.__fetchToIndex(index) > return self.__elements[index] E IndexError: list index out of range /opt/hostedtoolcache/Python/3.12.2/x64/lib/python3.12/site-packages/github/PaginatedList.py:77: IndexError ```
… chroot we don't care about
…t content into one comment body
39c8a9c
to
1d0cc61
Compare
This PR does many things.
the chroot column of the build matrix.