elastic / elastic/beats

[Flaky Test] github.com/elastic/beats/v7/filebeat/input/filestream TestFilestreamDeleteFileRemoveRetries

Open
#49,986 1 comment 0 reactions 0 assignees View on GitHub
flaky-test Team:Elastic-Agent-Data-Plane
Dominant language
Go
Stars
12.7k
Forks
5k
Avg merge
2d 1h
Merged PRs (30d)
370

Description

## Flaky Test

* **Test Name:** TestFilestreamDeleteFileRemoveRetries
* **Scope:** github.com/elastic/beats/v7/filebeat/input/filestream
* **File:** N/A
* **Location:** N/A
* **Buildkite Link:** https://buildkite.com/organizations/elastic/analytics/suites/beats/tests/6d825a36-1738-88f5-80e0-8b89a118d53e
* **Flaky Instances:** 1
* **Latest Occurrence:** 2026-04-08T08:07:25.717Z

### Details

```json
{
"id": "6d825a36-1738-88f5-80e0-8b89a118d53e",
"web_url": "https://buildkite.com/organizations/elastic/analytics/suites/beats/tests/6d825a36-1738-88f5-80e0-8b89a118d53e",
"scope": "github.com/elastic/beats/v7/filebeat/input/filestream",
"name": "TestFilestreamDeleteFileRemoveRetries",
"location": null,
"file_name": null,
"instances": 1,
"latest_occurrence_at": "2026-04-08T08:07:25.717Z",
"most_recent_instance_at": "2026-04-08T08:07:25.717Z",
"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/c4494b13-5e51-8634-b96e-9e34cbcb414c
**Time:** 2026-04-08T06:49:30.761Z
**Stacktrace:**

```
=== RUN TestFilestreamDeleteFileRemoveRetries
logger.go:108: Full logs written to ../../build/integration-tests/testing-logger-3982783572.log
--- FAIL: TestFilestreamDeleteFileRemoveRetries (1.01s)

```

Contributor guide

Open the contributing guide

Research direction

Start with TestFilestreamDeleteFileRemoveRetries in github.com/elastic/beats/v7/filebeat/input/filestream and reproduce it using the linked Buildkite run and failure logs. Trace the test and the file-removal retry behavior to identify the intermittent failure; done means the test reliably passes without masking a real failure.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.