test: update integration README #377
Conversation
henrywang
force-pushed
the
test_integration
branch
from
561f22b
to
a57898c
Compare
|
Looks like that run hit
...hmm, maybe the pull was slow? I did a blind attempt to add a pull before the run (with retries) to more cleanly separate network issues from install issues. |
Signed-off-by: Xiaofeng Wang <[email protected]> Signed-off-by: Colin Walters <[email protected]>
And add a retry loop. Signed-off-by: Colin Walters <[email protected]>
Not sure what was going wrong, we really need to collect the logs in this scenario instead of a hard timeout. Signed-off-by: Colin Walters <[email protected]>
cgwalters
force-pushed
the
test_integration
branch
from
efac006
to
09970d9
Compare
Github has job status update. Same job will have two status if testing farm updates PR status. That does not make sense. Github job status update can't be disabled, so testing farm PR job status update has to be disabled. Signed-off-by: Xiaofeng Wang <[email protected]>
|
@cgwalters There're two test status for one testing farm case (github job status and testing farm status). This does not make sense. Github job status update can't be disabled, so testing farm PR job status update has to be disabled. BTW: I filed two |
|
@cgwalters Can we use centos stream 9 image to test |
See #379 for that - it's unrelated and nonblocking. |
|
Cool, my untested ansible change worked 😄 |
Use
--tls-verify=falsein podman build, don't need CERT_URL secret any more.