register toolchain only for container exec and use it in py*_image #1173
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/gcbrun |
nlopezgi
force-pushed
the
fixPyToolchainError
branch
from
098608b to
a1c4205
Compare
nlopezgi
commented
Oct 2, 2019
| @@ -6,7 +6,7 @@ buildifier: | |||
| # are enabled except: | |||
| # rule-impl-return, uninitialized, return-value, rule-impl-return | |||
| # TODO (suvanjan): Re-enable once issues are fixed. | |||
| warnings: "attr-cfg,attr-license,attr-non-empty,attr-output-default,attr-single-file,confusing-name,constant-glob,ctx-actions,ctx-args,depset-iteration,depset-union,dict-concatenation,duplicated-name,filetype,function-docstring,git-repository,http-archive,integer-division,load,load-on-top,module-docstring,name-conventions,native-build,native-package,no-effect,out-of-order-load,output-group,package-name,package-on-top,positional-args,redefined-variable,repository-name,same-origin-load,string-iteration,unreachable,unsorted-dict-items,unused-variable" | |||
| warnings: "attr-cfg,attr-license,attr-non-empty,attr-output-default,attr-single-file,confusing-name,constant-glob,ctx-actions,ctx-args,depset-iteration,depset-union,dict-concatenation,duplicated-name,filetype,function-docstring,git-repository,http-archive,integer-division,load,load-on-top,module-docstring,name-conventions,native-build,native-package,no-effect,out-of-order-load,output-group,package-name,package-on-top,redefined-variable,repository-name,same-origin-load,string-iteration,unreachable,unsorted-dict-items,unused-variable" | |||
There was a problem hiding this comment.
removed "positional-args" due to bazelbuild/buildtools#726
nlopezgi
force-pushed
the
fixPyToolchainError
branch
8 times, most recently
from
18d24f2 to
78ec016
Compare
nlopezgi
force-pushed
the
fixPyToolchainError
branch
from
78ec016 to
7476ef4
Compare
|
/gcbrun |
nlopezgi
changed the title
|
/gcbrun |
nlopezgi
force-pushed
the
fixPyToolchainError
branch
3 times, most recently
from
47fd167 to
7daefb5
Compare
nlopezgi
force-pushed
the
fixPyToolchainError
branch
from
7daefb5 to
61b959d
Compare
nlopezgi
changed the title
|
/gcbrun |
|
/gcbrun |
nlopezgi
force-pushed
the
fixPyToolchainError
branch
from
a42ff6c to
9cff262
Compare
|
/gcbrun |
|
/gcbrun |
|
/gcbrun |
smukherj1
approved these changes
Oct 4, 2019
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nlopezgi, smukherj1 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The python toolchain we are registering for execution inside the container seems to be messing up with execution outside the container as documented here https://github.com/bazelbuild/rules_docker#known-issues-1.
target_compatible_withshould now be supported on all targets, so restricting our toolchain usingtarget_compatible_withshould make this error go away.See #1105