bazel-contrib / bazel-contrib/rules_go
Provide the ability to collect go_test cpu/memory profile
Open
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 760
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 12
Description
We can write them to `TEST_UNDECLARED_OUTPUTS_DIR` so that the user can inspect the content from the output.zip file.
Contributor guide
Research direction
Start at the go_test rule and examine how test outputs are collected. Verify how cpu and memory profiles can be written to TEST_UNDECLARED_OUTPUTS_DIR. Done means users can inspect those profiles in the output.zip file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100