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

bazel: test zlib-ng everywhere #17970

Closed

Conversation

keith
Copy link
Member

@keith keith commented Sep 2, 2021

I just want to see the CI run here

@repokitteh-read-only
Copy link

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #17970 was opened by keith.

see: more, trace.

@keith
Copy link
Member Author

keith commented Sep 21, 2021

looks like some issues that need to be debugged still exist here

@keith keith closed this Sep 21, 2021
@keith keith deleted the ks/bazel-test-zlib-ng-everywhere branch September 21, 2021 22:34
@keith keith restored the ks/bazel-test-zlib-ng-everywhere branch March 14, 2022 17:42
@keith keith reopened this Mar 14, 2022
I just want to see the CI run here

Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
@github-actions
Copy link

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Apr 14, 2022
@keith keith closed this Apr 14, 2022
@keith keith deleted the ks/bazel-test-zlib-ng-everywhere branch April 14, 2022 00:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant