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

Save injected metadata in RemoteActionFileSystem #16123

Closed
wants to merge 3 commits into from

Conversation

coeuvre
Copy link
Member

@coeuvre coeuvre commented Aug 18, 2022

So that spawn outputs can be accessed among Spwans within the same action using the FileSystem API.

This allow us to revert the hack we introduced in #12590. Also fixes the issue described by #15711.

Closes #15711.

…s can be accesssed among spwans within on action execution
@coeuvre coeuvre requested a review from a team as a code owner August 18, 2022 12:06
@brentleyjones
Copy link
Contributor

Should we cherry-pick this into 5.3?

@sgowroji sgowroji added team-Remote-Exec Issues and PRs for the Execution (Remote) team awaiting-review PR is awaiting review from an assigned reviewer labels Aug 18, 2022
@coeuvre
Copy link
Member Author

coeuvre commented Aug 18, 2022

I am fine to cherry-pick this into 5.3 but not sure whether it is still possible now to do so given that we are releasing 5.3 soon. cc @kshyanashree

@brentleyjones
Copy link
Contributor

I'll flag it, and it can get rejected/moved to the next release if it's too late.

@brentleyjones
Copy link
Contributor

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Aug 18, 2022
@ShreeM01 ShreeM01 removed the awaiting-review PR is awaiting review from an assigned reviewer label Sep 15, 2022
aiuto pushed a commit to aiuto/bazel that referenced this pull request Oct 12, 2022
So that spawn outputs can be accessed among Spwans within the same action using the `FileSystem` API.

This allow us to revert the hack we introduced in bazelbuild#12590. Also fixes the issue described by bazelbuild#15711.

Closes bazelbuild#15711.

Closes bazelbuild#16123.

PiperOrigin-RevId: 469133936
Change-Id: Ide5bcfa0fe2c6a3806d333cd61270e411aa78f80
@meteorcloudy
Copy link
Member

This should be in 6.0, removing the "potential release blocker" label.

@meteorcloudy meteorcloudy removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Remote-Exec Issues and PRs for the Execution (Remote) team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants