kubermatic / kubermatic/dashboard

Failing full-e2e CI Jobs

Open
#4,828 4 comments 0 reactions 0 assignees View on GitHub
kind/bug lifecycle/frozen sig/ui testing
Dominant language
Go
Stars
50
Forks
73
Avg merge
2d 22h
Merged PRs (30d)
31

Description

**Which jobs are failing?**:

- pre-dashboard-test-full-e2e
- pre-dashboard-test-full-e2e-ce

**Which test(s) are failing?**:
These jobs fail during the setup process.

**Prow link to failing test**:
These jobs are failing on all PRs (where these jobs are run) but here are the links to most recent failures:
- ` pre-dashboard-test-full-e2e`: https://public-prow.loodse.com/view/gs/prow-dev-public-data/pr-logs/pull/kubermatic_dashboard/4822/pre-dashboard-test-full-e2e/1559135496104316928
- `pre-dashboard-test-full-e2e-ce`: https://public-prow.loodse.com/view/gs/prow-dev-public-data/pr-logs/pull/kubermatic_dashboard/4822/pre-dashboard-test-full-e2e-ce/1559135496175620096

**Reason for failure**:
Needs investigation

**Anything else we need to know?**:

Contributor guide

Open the contributing guide

Research direction

Start with the linked Prow logs for pre-dashboard-test-full-e2e and pre-dashboard-test-full-e2e-ce, focusing on their setup failures. Trace the CI configuration and setup entry point responsible for both jobs; done means both jobs complete successfully on pull requests without masking test failures.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.