Skip to content

Update test2json.go#2873

Merged
linzhp merged 1 commit intobazel-contrib:masterfrom
uber-common:update-test2json
May 7, 2021
Merged

Update test2json.go#2873
linzhp merged 1 commit intobazel-contrib:masterfrom
uber-common:update-test2json

Conversation

@robbertvanginkel
Copy link
Copy Markdown
Contributor

What type of PR is this?
Bug fix

What does this PR do? Why is it needed?
There have been some updates to upstream's test2json.go since
we copied it at revision d47526, see https://github.com/golang/go/commits/master/src/cmd/internal/test2json/test2json.go. Most notably a fix for golang/go#40132, which golang itself backported to previous go versions.

This PR updates rules_go's copy of test2json.go to the latest.

Which issues(s) does this PR fix?

golang/go#40132

Other notes for review

There have been some updates to test2json.go since
d47526ed777958aa4a2542382e931eb7b3c4c6a9, most notably a fix for
golang/go#40132 that was important enough to
recevie a backport. Update rules_go's copy of test2json.go to the
latest.
@linzhp linzhp merged commit 71042b9 into bazel-contrib:master May 7, 2021
yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
Summary:
- `pep508_deps` is now much simpler, because the hard work is done in
  analysis phase
- `whl_library` BUILD.bazel tests now also have a test for the legacy
  flow.

One thing that I noticed is that now we have an implicit dependency on
the python toolchain when getting all of the `whl` target tree. This is
a filegroup target that includes dependent wheels. However, we fallback
to the flag values if we don't have the toolchain, so we should be good
in general.

Overall I like how this is turning out because we don't need to pipe the
`target_platforms` anymore when we enable `PIPSTAR` feature. This means
that we can start creating fewer whl_library instances - e.g. a
`py3-none-any` wheel can be fetched once instead of once per python
interpreter version. I'll leave this optimization for a later time.

Work towards bazel-contrib#260

---------

Co-authored-by: Richard Levasseur <richardlev@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants