Open danielsiwiec opened 4 years ago
Hi @danielsiwiec. 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.
/lgtm /approve Thank you for the fix!
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Bobgy, danielsiwiec
To complete the pull request process, please assign gaoning777 after the PR has been reviewed.
You can assign the PR to them by writing /assign @gaoning777
in a comment when ready.
The full list of commands accepted by this bot can be found here.
@danielsiwiec: The following test failed, say /retest
to rerun all failed tests:
Test name | Commit | Details | Rerun command |
---|---|---|---|
kubeflow-metadata-presubmit | 8dbe3b2d8c9886dc8d7ff3661faaa7b037c0aa41 | link | /test kubeflow-metadata-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.
I'm sorry, this repo is pretty much in an abandoned state. We'll continue to evolve the metadata story, but may not be based on this repo. If presubmit is broken, then we won't accept any new PRs.
/retest
@danielsiwiec: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
Check out this pull request on
See visual diffs & provide feedback on Jupyter Notebooks.
Powered by ReviewNB