crl-release-26.2: nightly linux-stress tests failed

Open
#6,250 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
github-actions, go
Domain
databases, testing

Research direction

Start from the linked GitHub Actions run and find the failing linux-stress test and its log output at commit e014faaa4604ca4c9d7d146f40cb3fd152f150e9. Try to reproduce the failure locally with the same Go version (1.25) and the stress test invocation from the CI workflow. Done means the root cause is identified and either fixed or documented on the issue, with the failing test passing under repeated runs.

Written by the indexing model from the issue text.

Description

C-test-failure

The nightly linux-stress test run failed on e014faaa4604ca4c9d7d146f40cb3fd152f150e9 (go1.25). Please review the run here.

Jira issue: PEBBLE-1705

Dominant language
Go
Stars
6.1k
Forks
608
Avg merge
16h 40m
Merged PRs (30d)
9

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cockroachdb/pebble

All issues in cockroachdb/pebble

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.