|
Smoke Test / Run basic test suite (push) Failing after 6s
Details
K8s Deploy Test / Run deploy test suite on kind/k8s (push) Failing after 3s
Details
Lint Checks / Run linter (push) Failing after 3s
Details
Publish / Build and publish (push) Failing after 5s
Details
Container Registry Test / Run contaier registry hosting test on kind/k8s (push) Failing after 3s
Details
Database Test / Run database hosting test on kind/k8s (push) Failing after 4s
Details
Deploy Test / Run deploy test suite (push) Failing after 3s
Details
Webapp Test / Run webapp test suite (push) Failing after 3s
Details
Fixturenet-Laconicd-Test / Run Laconicd fixturenet and Laconic CLI tests (push) Failing after 4s
Details
Part of https://www.notion.so/Alerting-for-failing-CI-jobs-d0183b65453947aeab11dbddf989d9c0 - Run CI alert steps only on main to avoid alerts for in-progress PRs - The Slack alerts will be sent on a CI job failure if - A commit is pushed directly to main - A PR gets merged into main - A scheduled job runs on main Reviewed-on: https://git.vdb.to/cerc-io/stack-orchestrator/pulls/797 Co-authored-by: Prathamesh Musale <prathamesh.musale0@gmail.com> Co-committed-by: Prathamesh Musale <prathamesh.musale0@gmail.com> |
||
|---|---|---|
| .. | ||
| triggers | ||
| fixturenet-eth-plugeth-arm-test.yml | ||
| fixturenet-eth-plugeth-test.yml | ||
| fixturenet-eth-test.yml | ||
| fixturenet-laconicd-test.yml | ||
| lint.yml | ||
| publish.yml | ||
| test-container-registry.yml | ||
| test-database.yml | ||
| test-deploy.yml | ||
| test-k8s-deploy.yml | ||
| test-webapp.yml | ||
| test.yml | ||