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

Make the RemoteSpawnRunner and RemoteSpawnCache async #7182

Closed
buchgr opened this issue Jan 18, 2019 · 2 comments
Closed

Make the RemoteSpawnRunner and RemoteSpawnCache async #7182

buchgr opened this issue Jan 18, 2019 · 2 comments
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Remote-Exec Issues and PRs for the Execution (Remote) team type: feature request

Comments

@buchgr
Copy link
Contributor

buchgr commented Jan 18, 2019

In order to support the upcoming fix for #6394. This will allow us to fully utilize the parallelism offered by a remote execution system.

@buchgr buchgr added type: feature request team-Remote-Exec Issues and PRs for the Execution (Remote) team labels Jan 18, 2019
@buchgr buchgr self-assigned this Jan 18, 2019
@buchgr buchgr added the P2 We'll consider working on this in future. (Assignee optional) label Jan 18, 2019
@buchgr buchgr removed their assignment Jan 9, 2020
@github-actions
Copy link

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 3 years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

@github-actions github-actions bot added the stale Issues or PRs that are stale (no activity for 30 days) label Feb 28, 2023
@github-actions
Copy link

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) stale Issues or PRs that are stale (no activity for 30 days) team-Remote-Exec Issues and PRs for the Execution (Remote) team type: feature request
Projects
None yet
Development

No branches or pull requests

1 participant