Skip to content
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.

Sign up for GitHub

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

Jump to bottom

The frontend-integration-test is really flaky #272

Closed
Ark-kun opened this issue Nov 15, 2018 · 5 comments
Closed

The frontend-integration-test is really flaky #272

Ark-kun opened this issue Nov 15, 2018 · 5 comments
Assignees
@yebrahim @gaoning777
Labels
priority/p0

Comments

@Ark-kun
Copy link
Contributor

Ark-kun commented Nov 15, 2018

https://gubernator.k8s.io/builds/kubernetes-jenkins/pr-logs/directory/presubmit-e2e-test?
@Ark-kun
Copy link
Contributor Author

Ark-kun commented Nov 15, 2018

The sample tests should not have any effect on the frontend tests, but there might be some relation.

@yebrahim
Copy link
Contributor

yebrahim commented Nov 15, 2018 •
edited
Loading

They run in parallel with frontend integration tests, but this wasn't a consideration when building the latter, that's why I think it's the culprit.

@IronPan IronPan mentioned this issue Nov 15, 2018
Merged
@gaoning777
Copy link
Contributor

I checked all the failures and the majority of them failed due to two reasons:
1). cluster got deleted accidentally, it might've been accidentally deleted manually.
2). cannot create cluster due to computing/disk quota.
There is only one test failure due to "cannot connect to the docker daemon...".

I do not think it is related to the frontend integration tests.

@rileyjbauer
Copy link
Contributor

Is this issue still affecting anyone?

@IronPan IronPan mentioned this issue Nov 17, 2018
Merged
@gaoning777
Copy link
Contributor

Free feel to reopen if necessary.

Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
@richardsliu @k8s-ci-robot
Add richardsliu as OWNER (kubeflow#272)
ac58d1c
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this issue Mar 11, 2024
@Tomcli @animeshsingh
feat(samples): parameterize storageclass for the e2e-mnist example (k…
b2d5b19 
…ubeflow#272)

* parameterize storageclass for the e2e-mnist example

* update notebook readme for how to figure out the correct storageclass

* Add RWM storageclass as prereq

* Update samples/e2e-mnist/mnist.ipynb

Co-authored-by: Animesh Singh <singhan@us.ibm.com>

Co-authored-by: Animesh Singh <singhan@us.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yebrahim yebrahim

@gaoning777 gaoning777

Labels
priority/p0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@yebrahim @Ark-kun @gaoning777 @rileyjbauer