Repository navigation
ci: move system tests from Github Actions to Testing Farm - #9304
Conversation
ef7f7e8 to
400131b
Compare
|
Note: Do not forget to switch sssd-ci-containers repo in the test plan after SSSD/sssd-ci-containers#219 is merged. |
afee380 to
482ba1f
Compare
|
/packit build |
1 similar comment
|
/packit build |
b8273c4 to
fa6197b
Compare
66e45be to
752e0b5
Compare
|
/packit check |
|
There appears to be a syntax error in the command provided. Please refer to the Packit documentation or use the |
|
/packit test |
1 similar comment
|
/packit test |
|
I get this failure on centos-10... it is a segfault in autofs, I can't reproduce this locally so I'm trying to catch it in reserved TF run. Other two errors are in provisioning phase. Both looks like a network error. On TF side, reported, they will implement a retry Other one gets further but fails when downloading containers. I implemented a retry on our side. |
|
/packit retest-failed |
1 similar comment
|
/packit retest-failed |
|
Looks like |
No, good catch. I wanted to add it to static analyzers but forgot. Done. |
340b5b0 to
c7d2537
Compare
|
f-45: "Request was canceled on user request." -- why? |
Dunno. I can see there is SIGTERM in setup (TF not ours). I asked, waiting for answer. |
|
Perhaps not related to this PR, but looking at logs (even at Rawhide): (1) why there are so many (2) stdout or stderr leaks to pytest output? |
Sorry, it was accidentally. |
|
@alexey-tikhonov the packit issue is being discussed here: https://redhat-internal.slack.com/archives/C04MU29TES1/p1792506940634379 Most probably some race, but did not yet get full answer |
It's not error in the test run, these tests are really skipped and they call
No. This is a skip reason from detect_pinpad_reader. But malformed. For some reason, other skip reasons are not printed. I did not look into it yet, but I do not think it should prevent us moving forward with this PR. It is not caused by it, it is present in GH as well.
|
I wanted to double check the reason isn't some difference in TF env. Feel free to merge. |
This enables automatic collection of coredumps, failing test if the coredumps occurs in any SSSD binary. Other coredumps will be ignored if test is passed. All coredumps are collected if test fails. Reviewed-by: Justin Stephenson <jstephen@redhat.com>
The system tests can quickly deplete available Github runners (20) and we need them for process purposes (Accepted label). So we keep only quick checks in GHA now. Testing Farm is supported infrastructure for Fedora Project, we should be able to see infra issues resolved more quickly as we can actually ping people when needed. Reviewed-by: Justin Stephenson <jstephen@redhat.com>
This is a quick job and we can run it immediately without waiting for the rpms to be built. Reviewed-by: Justin Stephenson <jstephen@redhat.com>
The system tests can quickly deplete available Github runners (20)
and we need them for process purposes (Accepted label). So we keep
only quick checks in GHA now.
Testing Farm is supported infrastructure for Fedora Project, we should
be able to see infra issues resolved more quickly as we can actually
ping people when needed.