-
Notifications
You must be signed in to change notification settings - Fork 1k
ci: trigger zombienet tests automatically #9960
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
base: master
Are you sure you want to change the base?
Conversation
… zombienet-fix-process-logs
… zombienet-workflow-call # Conflicts: # .github/workflows/zombienet-reusable-preflight.yml
Thanks @DenzelPenzel , looks good but I think this |
6a935ec
to
acc5e0f
Compare
79857a4
to
a0e85af
Compare
a0e85af
to
75c8399
Compare
All GitHub workflows were cancelled due to failure one of the required jobs. |
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.
Looks good, thanks!!
It looks that there is a deadlock that prevents zombienet tests from starting: https://github.com/paritytech/polkadot-sdk/actions/runs/18356902291
|
hmm, thanks @alvicsam. I will check this erros. |
@alvicsam concurrency issue is now fixed, but all the test are show in the build workflow which is not good for discovery. ![]() |
I don't see the problem of discoverability. All zombienet jobs are in the same list of jobs in the github UI but the name is slightly different. We can change the workflow name if you want. I would prefer not adding a off-topic: there is one job that often exceeds timeout |
Yes, that test is disabled as part of this pr https://github.com/paritytech/polkadot-sdk/pull/9957/files#r2416989294. Thx! |
Description
#9877