-
Notifications
You must be signed in to change notification settings - Fork 699
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
Integrate with Prow for Continuous Testing #46
Comments
Initial ProwJobs were defined in kubernetes/test-infra/pull/4951. Next steps
|
Status
|
the periodic job was keep failing without logs - http://prow.k8s.io/?type=periodic&job=mlkube-build-periodic, I'll retrigger and see what is going on pr/postsubmit jobs probably need a different log path in testgrid |
|
@krzyzacy ; thanks. I'll put together a fix for the periodic issue. |
#56 hopefully fixes the periodic test; should run every 8 hours so should know tomorrow morning. |
@krzyzacy My fix for the periodic jobs doesn't appear to have worked. Could you check the logs or tell me how I can check them? |
the job comes from http://prow.k8s.io/?job=mlkube-build-periodic, but since it failed early on, it did not upload any logs :-( and the failing pod will be deleted within next hour.. You can try click rerun and run the kubectl command it pops up. (I'll retrigger and check the log) |
@krzyzacy Thanks; I was looking at the wrong tab; http://prow.k8s.io/?repo=jlewi%2Fmlkube.io. I realize now periodic jobs don't specify the repository so they wouldn't show up under the repository tab. Here's the error; another bug on my end.
|
k8s-bot integration is now working; see #50 |
Filed #59 to fix an issue with presubmits. |
#59 is fixed Periodic jobs are fixed. http://prow.k8s.io/?job=mlkube-build-periodic |
All blocking issues have been fixed. Prow integration is all setup. |
We would like to integrate with Prow, K8s, test infra to provide continuous testing.
After some initial discussion with @foxish and @krzyzacy the current plan is to have 2 prow jobs;
The current plan is to not rely on helm test but just to write go tests as necessary.
First step is probably to create a prow job to build and push the Docker image.
Remaining Issues Blocking This Issue
Post submit jobs don't correctly upload artifacts to GCS #62 Post submit jobs not uploaded correctlyNo results show up in prow test grid for presubmit jobs #75 Presubmit results not showing up in test gridNo results show up if you click on mlkube-build-periodic #76 No results show up for periodic jobsrunner.py needs to create build-log.txt with stdout/stderr of test #82 Need to copy stdout/stderr of tests to GCS.Update prow to use repo tensorflow/k8s #84 Update prow to use tensorflow/k8spostsubmit results aren't showing up in testrgrid #113 postsubmit results show up in test gridThe text was updated successfully, but these errors were encountered: