prometheus / prometheus/node_exporter
Fail to test with version 1.3.1 under RISC-V
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.8k
- Forks
- 2.7k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 8
Description
Host operating system: output of uname -a
Linux 5.11.0-1017-generic #18-Ubuntu SMP riscv64 GNU/Linux
node_exporter version: output of node_exporter --version
1.3.1
node_exporter command line flags
Are you running node_exporter in Docker?
What did you do that produced an error?
make collector/fixtures/sys/.unpacked
go test ./...
./end-to-end-test.sh
What did you expect to see?
What did you see instead?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading test.log and reproducing the listed commands: make collector/fixtures/sys/.unpacked, go test ./..., and ./end-to-end-test.sh on the RISC-V host. Compare the failures with the test and fixture areas identified by the output; done means the relevant test commands pass under RISC-V.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- operating-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100