Test: E2E smoke tests integration - DO NOT MERGE #174
Conversation
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed on the GitHub Actions runner and connected directly to the E2E cluster. Download logs: |
Signed-off-by: Nikolay Demchuk <[email protected]>
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator Smoke tests failed! Tests were executed in a Kubernetes Job in the e2e cluster (hypervisor environment). View Details
View logs in cluster: kubectl logs -n undefined -l job-name=undefined |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator Smoke tests failed! Tests were executed in a Kubernetes Job in the e2e cluster (hypervisor environment). View Details
View logs in cluster: kubectl logs -n undefined -l job-name=undefined |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator Smoke tests failed! Tests were executed in a Kubernetes Job in the e2e cluster (hypervisor environment). View Details
View logs in cluster: kubectl logs -n undefined -l job-name=undefined |
Signed-off-by: Nikolay Demchuk <[email protected]>
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ✅Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk <[email protected]>
E2E Smoke Tests Results ❌Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
E2E Smoke Tests Results ✅Module: sds-node-configurator View Details
Tests were executed directly on the GitHub Actions runner against the e2e cluster. Artifacts: Test logs are available in workflow artifacts (if any). |
Signed-off-by: Nikolay Demchuk [email protected]
Description
Build and push for dev now has an e2e-tests step
Why do we need it, and what problem does it solve?
Now developers can automatically trigger essential tests for their pull requests by applying e2e-smoke-test label on their PR
What is the expected result?
Checklist