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

Backport "Make legacy artifact -> packages -> distribtest jobs a noop" to v1.49.x #31664

Closed
wants to merge 1 commit into from

Conversation

apolcyn
Copy link
Contributor

@apolcyn apolcyn commented Nov 15, 2022

Attempt to build packages successfully on v1.49.x

Currently, the macos artifact build job is failing to install dependencies.

@jtattermusch
Copy link
Contributor

@apolcyn I suspect this might not be what you want. If you provided the link to the failed build, I'd know more.

If you're actually trying to build the artifacts / packages on 1.49.x (rather than just trying to silence an error), this PR is likely not going to help you. I suspect the macos artifact build might be failing because of the recent MacOS monterey migration?

You might want to backport e.g. this instead: #31125

@apolcyn
Copy link
Contributor Author

apolcyn commented Nov 17, 2022

@jtattermusch there were Ruby and Python setup failures in the macos artifact build job.

The ruby failure was here: https://fusion2.corp.google.com/invocations/e4fd00c9-d2ae-40e1-915a-36150d86eb44/targets/grpc%2Fcore%2Fmaster%2Fmacos%2Fgrpc_build_artifacts/log. This PR would stop trying to use macos entirely, for the ruby artifact build.

I can't find the link to the Python failure, but it was happening on this command, I believe because it couldn't find python2.7. This PR would stop using that script entirely.

@jtattermusch
Copy link
Contributor

From your log:

++ rvm get stable
Archives path '/Users/kbuilder/.rvm/archives' not writable, aborting.

would be addressed by #31125.

@jtattermusch
Copy link
Contributor

I created #31697.

The python issue would IMHO be addressed by backporting #31126.

A PHP fix is here: #31567 (also backport if that's what you need).

@jtattermusch
Copy link
Contributor

Looks like this was superseded. I'm going to close, feel free to reopen if still needed.

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.

None yet

3 participants