elastic / elastic/beats

[Flaky Test] x-pack/filebeat/input/netflow TestNetFlow/ipfix_cisco.reversed

Open
#43,670 6 comments 0 reactions 1 assignee View on GitHub

@haetamoudi is already working on this.

Since Aug 6, 2025.

Filebeat flaky-test Team:Security-Deployment and Devices
Dominant language
Go
Stars
12.7k
Forks
5k
Avg merge
2d 1h
Merged PRs (30d)
370

Description

## Flaky Test

* **Test Name:** TestNetFlow/ipfix_cisco.reversed
* **Link:** https://github.com/elastic/beats/blob/10858f98cf8f14e1de51b195bba607c784bc6c90/x-pack/filebeat/input/netflow/netflow_test.go#L151-L153
* **Branch:** https://github.com/elastic/beats/pull/43661
* **Artifact Link:** [1](https://github.com/elastic/beats/actions/runs/14242028202/job/39913931551?pr=43661#step:3:691)
* **Notes:** The timeout for this assertion is 5s, that could be too low which is causing the flakiness.

### Stack Trace

```
=== Failed
=== FAIL: x-pack/filebeat/input/netflow TestNetFlow/ipfix_cisco.reversed (5.10s)
netflow_test.go:151:
Error Trace: /Users/runner/work/beats/beats/x-pack/filebeat/input/netflow/netflow_test.go:151
Error: Condition never satisfied
Test: TestNetFlow/ipfix_cisco.reversed
Messages: got a different number of events than expected

=== FAIL: x-pack/filebeat/input/netflow TestNetFlow (5.72s)
```

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.