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

[internal] go: switch test analysis to use go tool's code plus more tests #13100

Merged
merged 2 commits into from
Oct 4, 2021

Conversation

tdyas
Copy link
Contributor

@tdyas tdyas commented Oct 4, 2021

Changes to the tests analysis code:

  • Switch the test analysis code to use the go tool's code instead of the code from Bazel rules_go.
  • Analyze testable examples as well.
  • Add more tests of the analysis including incorrect signatures and multiple TestMain functions.

[ci skip-rust]

[ci skip-build-wheels]

[ci skip-rust]

[ci skip-build-wheels]
Copy link
Contributor

@Eric-Arellano Eric-Arellano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

[ci skip-rust]

[ci skip-build-wheels]
@tdyas tdyas merged commit 8a28a4b into pantsbuild:main Oct 4, 2021
@tdyas tdyas deleted the golang_more_tests_analysis branch October 4, 2021 23:58
Eric-Arellano pushed a commit to Eric-Arellano/pants that referenced this pull request Oct 5, 2021
… tests (pantsbuild#13100)

Changes to the tests analysis code:

- Switch the test analysis code to use [the `go` tool's code](https://github.com/golang/go/blob/master/src/cmd/go/internal/load/test.go) instead of the code from Bazel rules_go.
- Analyze testable examples as well.
- Add more tests of the analysis including incorrect signatures and multiple `TestMain` functions. 

[ci skip-rust]

[ci skip-build-wheels]
@stuhood stuhood mentioned this pull request Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants