bazel-contrib / bazel-contrib/rules_go
Fix or skip tests that fail in remote execution
Open
code-health
remote-execution
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 760
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 12
Description
A number of tests were disabled in the RBE CI configuration in #1638. They were:
* `//:vet`
* `//tests/core/go_path:go_path_test`
* `//tests/core/stdlib:buildid_test`
* `@com_github_mattn_go_sqlite3//:go_default_test`
We should analyze why these tests were failed and either fix them or document why they need to be skipped.
Contributor guide
Research direction
Review the RBE CI configuration changes in #1638 and investigate the four named targets: //:vet, //tests/core/go_path:go_path_test, //tests/core/stdlib:buildid_test, and @com_github_mattn_go_sqlite3//:go_default_test. Reproduce their remote-execution failures, then either fix the tests or document why each must remain skipped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, ci-cd, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100