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.

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

Marking the UI-metadata and Metrics artifacts as optional #1260

Conversation

Ark-kun
Copy link
Contributor

@Ark-kun Ark-kun commented Apr 29, 2019

Argo has recently fixed a bug argoproj/argo-workflows#1277 . Now the workflows with incorrect missing output artifacts will start failing.
Most of the workflows that have been produced since https://github.com/googleprivate/ml/pull/878 and https://github.com/googleprivate/ml/pull/1311 have been broken. I've tried to prevent this but people did not listen.

Now we have to scramble to fix this messy problem when there are hundreds of broken compiled pipeline packages.

This PR is the first step in the process outlined in #1250 (comment)

This change is Reviewable

@@ -193,6 +193,10 @@ def _op_to_template(op: BaseOp):
for name, path in output_artifact_paths.items()
]

for output_artifact in output_artifacts:
if output_artifact['name'] in ['mlpipeline-ui-metadata', 'mlpipeline-metrics']:
output_artifact['optional'] = True
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this field working with current argo image?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes =)
I've discovered that Argo is using slightly broken way to parse YAML, so unknown fields are ignored.
Let's see what the tests say.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All tests have passed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see the sample test passing for the last commit. Actually, it seems that it didn't run for the last commit. Do you know why?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It did. https://prow.k8s.io/pr-history/?org=kubeflow&repo=pipelines&pr=1260
But the unfinished tests are often shown at the rightmost column under the "Unknown" commit label.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sg. thanks.

/lgtm

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

// When I wrote the comment that the tests have passed, the sample test has already completed the main part and was deleting the cluster. I guess, when you've looked at it, the Prow still has not detected it as finished.

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Ark-kun

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 6b0d4d1 into kubeflow:master Apr 30, 2019
@Ark-kun Ark-kun deleted the Marking-the-UI-metadata-and-Metrics-artifacts-as-optional branch April 30, 2019 01:02
@gaoning777
Copy link
Contributor

Add a argo PR link: argoproj/argo-workflows#1277 as reference.

@Ark-kun
Copy link
Contributor Author

Ark-kun commented May 9, 2019

Add a argo PR link: argoproj/argo#1277 as reference.

Done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants