scylladb / scylladb/cpp-rs-driver
Add a way to inspect driver logs during CI
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26
- Forks
- 19
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 7
Description
When running the tests in build folder, the test binary generates a log directory which contains driver (tracing) logs. I often use these during debugging - e.g. to see why the test is failing or what needs to be adjusted.
Sometimes, there may be a test that fails during CI, but we are not able to reproduce it locally. We should add a way to export the log directory with the driver logs during CI.
Contributor guide
No contributing guide indexed for this repository
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 with the CI configuration and the test invocation for the build folder, then confirm where the generated log directory is available. Done means CI preserves the driver tracing logs from that directory as an accessible exported artifact when tests run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100