chore(tests): create a test to check whether requirements.txt was generated with pip-compile

[mahdikhashan]

Description of your changes:
resolves #11495

Checklist:

• You have signed off your commits
• The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.

[google-oss-prow]

Hi @mahdikhashan. 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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[mahdikhashan]

@hbelmiro i kindly request for your review on this pr. thanks

[hbelmiro]

/ok-to-test

[github-actions]

Approvals successfully granted for pending runs.

[hbelmiro]

Can we rename this file to requirements-txt-automatically-generated.yaml?

[mahdikhashan]

done.

[hbelmiro]

@mahdikhashan can you please link this PR to the issue?

[mahdikhashan]

@mahdikhashan can you please link this PR to the issue?

done

[mahdikhashan]

I'm facing the same issue: google/ml-metadata#191 (comment), @hbelmiro

since i'm on mac with m cpu, i could't use the update_requirements.sh script - the docker image was only for amd64. any tips on overcoming? shall i add a build script for this package? (to build it with cpython in a docker file?)

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chensun, hbelmiro for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• .github/OWNERS
• backend/OWNERS
• sdk/OWNERS
• test/OWNERS

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

[mahdikhashan]

@hbelmiro would you please run the test once more? in addition, on mac m1, i couldnt compile the requirements for ml-metadata and visualisation. i appreciate any hints.

[hbelmiro]

/ok-to-test

[github-actions]

Approvals successfully granted for pending runs.

[hbelmiro]

on mac m1, i couldnt compile the requirements for ml-metadata and visualisation. i appreciate any hints.

@mahdikhashan what do you see?

[mahdikhashan]

on mac m1, i couldnt compile the requirements for ml-metadata and visualisation. i appreciate any hints.

@mahdikhashan what do you see?

for metadata, the same issue as here: google/ml-metadata#191 (comment)

for visulization, the building of packages (c language) are failing.

[hbelmiro]

on mac m1, i couldnt compile the requirements for ml-metadata and visualisation. i appreciate any hints.

@mahdikhashan what do you see?

for metadata, the same issue as here: google/ml-metadata#191 (comment)

for visulization, the building of packages (c language) are failing.

@mahdikhashan have you taken a look at this comment?
I'd say to not invest much time on this. If you can't make it work, just copy the result of the workflow you're creating.

[mahdikhashan]

on mac m1, i couldnt compile the requirements for ml-metadata and visualisation. i appreciate any hints.

@mahdikhashan what do you see?

for metadata, the same issue as here: google/ml-metadata#191 (comment)

for visulization, the building of packages (c language) are failing.

@mahdikhashan have you taken a look at this comment?
I'd say to not invest much time on this. If you can't make it work, just copy the result of the workflow you're creating.

ok, I'll try to copy the workflow result. (I saw the mentioned comment but didn't try it)

[hbelmiro]

on mac m1, i couldnt compile the requirements for ml-metadata and visualisation. i appreciate any hints.

@mahdikhashan what do you see?

for metadata, the same issue as here: google/ml-metadata#191 (comment)
for visulization, the building of packages (c language) are failing.

@mahdikhashan have you taken a look at this comment?
I'd say to not invest much time on this. If you can't make it work, just copy the result of the workflow you're creating.

ok, I'll try to copy the workflow result. (I saw the mentioned comment but didn't try it)

@mahdikhashan don't do that for all files though. If you face new issues, ne need to assess them.

[mahdikhashan]

on mac m1, i couldnt compile the requirements for ml-metadata and visualisation. i appreciate any hints.

@mahdikhashan what do you see?

for metadata, the same issue as here: google/ml-metadata#191 (comment)
for visulization, the building of packages (c language) are failing.

@mahdikhashan have you taken a look at this comment?
I'd say to not invest much time on this. If you can't make it work, just copy the result of the workflow you're creating.

ok, I'll try to copy the workflow result. (I saw the mentioned comment but didn't try it)

@mahdikhashan don't do that for all files though. If you face new issues, ne need to assess them.

ok, i updated the visualization requirements. would you please trigger the tests again.

[hbelmiro]

/ok-to-test

[hbelmiro]

We can't leave the full path because developers will run pip-compile from the directory where the requirements.in file is.
I think we can achieve the same behaviour in the CI by using working-directory.

[mahdikhashan]

ok, i'll fix it.

[mahdikhashan]

done

[hbelmiro]

/ok-to-test

[github-actions]

Approvals successfully granted for pending runs.

[hbelmiro]

/ok-to-test

[github-actions]

Approvals successfully granted for pending runs.

[hbelmiro]

/ok-to-test

[github-actions]

Approvals successfully granted for pending runs.