Open yashjakhotiya opened 4 years ago
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jinchihe
You can assign the PR to them by writing /assign @jinchihe
in a comment when ready.
The full list of commands accepted by this bot can be found here.
Hi @yashjakhotiya. Thanks for your PR.
I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/assign @jinchihe
/ok-to-test
/retest
@jinchihe this is only a documentation update. Ideally, this should not fail any presubmit test.
@jinchihe this is only a documentation update. Ideally, this should not fail any presubmit test.
Yeah, that should be caused by test tenv, I will take a look later once get chance. Thanks.
/retest
@yashjakhotiya: The following test failed, say /retest
to rerun all failed tests:
Test name | Commit | Details | Rerun command |
---|---|---|---|
kubeflow-fairing-presubmit | 0505b25e0728a892768340a56f159a0b55fd0cd8 | link | /test kubeflow-fairing-presubmit |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
@yashjakhotiya The CI testing problem has been fixed, would you please fetch and rebase? thanks a lot!
What this PR does / why we need it: Without documentation, users might struggle in installation of additional python packages in the built docker image required for fairing jobs. This PR mentions the special role of 'requirements.txt' in input_files list of ml_tasks.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged): Fixes #NONESpecial notes for your reviewer:
This is a documentation update PR
Release note: