[Flaky Test] github.com/elastic/beats/v7/filebeat/input/journald/pkg/journalctl TestNewFactoryChroot
- Dominant language
- Go
- Stars
- 12.7k
- Forks
- 5k
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 370
Description
## Flaky Test
* **Test Name:** TestNewFactoryChroot
* **Scope:** github.com/elastic/beats/v7/filebeat/input/journald/pkg/journalctl
* **File:** N/A
* **Location:** N/A
* **Buildkite Link:** https://buildkite.com/organizations/elastic/analytics/suites/beats/tests/fa07b7a8-c4d5-8414-a4b1-8ad62dc53105
* **Flaky Instances:** 1
* **Latest Occurrence:** 2026-04-01T16:03:17.955Z
### Details
```json
{
"id": "fa07b7a8-c4d5-8414-a4b1-8ad62dc53105",
"web_url": "https://buildkite.com/organizations/elastic/analytics/suites/beats/tests/fa07b7a8-c4d5-8414-a4b1-8ad62dc53105",
"scope": "github.com/elastic/beats/v7/filebeat/input/journald/pkg/journalctl",
"name": "TestNewFactoryChroot",
"location": null,
"file_name": null,
"instances": 1,
"latest_occurrence_at": "2026-04-01T16:03:17.955Z",
"most_recent_instance_at": "2026-04-01T16:03:17.955Z",
"last_resolved_at": null,
"ownership_team_ids": [],
"failure_examples_count": 1
}
```
### Failure Examples
**Example 1:**
**Run:** https://api.buildkite.com/v2/analytics/organizations/elastic/suites/beats/runs/1d369cd6-43e0-8c4c-9ff2-dcc01f60b76b
**Time:** 2026-04-01T15:56:57.317Z
**Stacktrace:**
```
=== RUN TestNewFactoryChroot
chroot_test.go:140: Container is stuck, stopping the test. Look at the container logs for more information.
fs.go:101: Temporary directory saved: /opt/buildkite-agent/builds/bk-agent-prod-gcp-1775058797787563364/elastic/filebeat/filebeat/build/integration-tests/TestNewFactoryChroot2860672267
--- FAIL: TestNewFactoryChroot (40.25s)
```
Contributor guide
Research direction
Start by reading the failure at chroot_test.go:140 for TestNewFactoryChroot and inspect the container logs saved in the temporary directory shown in the failure. Use the linked Buildkite run to compare the flaky failure with successful runs. Done means the test no longer gets stuck and passes reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100