Prow code, test image code and code being tested can still desync. #198
Assignees
Comments
|
Please see comment in #196 for more details. |
|
Fixed in #315 |
Linchin
pushed a commit
to Linchin/pipelines
that referenced
this issue
Apr 11, 2023
* name is used in the XMl file containing the test results. If name isn't set the XML file won't be created correctly and therefore not surfaced in gubernator correctly; see kubeflow/kubeflow#1426 * Related to kubeflow/kubeflow#1426
m-rafeeq
referenced
this issue
in m-rafeeq/data-science-pipelines
Jan 21, 2025
…ct-manager-reqs fix(backend): Update Artifact Manager Dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When Prow runs tests it clones the repo and merges the PR branch into master at time T0. This includes
test/presubmit_tests.shandtest/*.yamlWhen build-image builds test images, it clones the repo and merges the PR branch into master at time ~T1 separately for each image. This includes
test/*/run_test.shand the whole frontend test suiteWhen a test runs, it clones the repo and merges the PR branch into master at time ~T2 separately for each test.
This was the issue that most likely caused #196
That issue got fixed when I explicitly re-run build-image step for all problematic PRs.
I do not fully understand how the unit test image has caused problem, since it should only contain the
run_test.shscript and couple of Go packages.The text was updated successfully, but these errors were encountered: