elastic / elastic/beats

[flaky-test] Auditbeat file_integrity TestConfig failing on Windows 2022 with Go 1.22

Open Beginner friendly
#40,087 3 comments 0 reactions 0 assignees View on GitHub
Auditbeat flaky-test Team:Security-Service Integrations
Dominant language
Go
Stars
12.7k
Forks
5k
Avg merge
2d 15m
Merged PRs (30d)
385

Description

## Flaky Test

* **Test Name:** auditbeat/module/file_integrity TestConfig
* **Link:** https://buildkite.com/elastic/auditbeat/builds/6128#019078f8-e76d-40c4-b2eb-318b3d80d13a
* **Branch:** https://github.com/elastic/beats/pull/40082
* **Notes:** This is a test failure for the upgrade from Go 1.21 to Go 1.22.

### Stack Trace

```
=== Failed
=== FAIL: auditbeat/module/file_integrity TestConfig (0.00s)
config_test.go:57:
Error Trace: C:/buildkite-agent/builds/bk-agent-prod-gcp-1720016509040597440/elastic/auditbeat/auditbeat/module/file_integrity/config_test.go:57
Error: Not equal:
expected: "\\.DS_Store(?-m:$)"
actual : "(?-m:\\.DS_Store$)"
Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-\.DS_Store(?-m:$)
+(?-m:\.DS_Store$)
Test: TestConfig
config_test.go:58:
Error Trace: C:/buildkite-agent/builds/bk-agent-prod-gcp-1720016509040597440/elastic/auditbeat/auditbeat/module/file_integrity/config_test.go:58
Error: Not equal:
expected: "\\.swp(?-m:$)"
actual : "(?-m:\\.swp$)"
Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-\.swp(?-m:$)
+(?-m:\.swp$)
Test: TestConfig
config_test.go:60:
Error Trace: C:/buildkite-agent/builds/bk-agent-prod-gcp-1720016509040597440/elastic/auditbeat/auditbeat/module/file_integrity/config_test.go:60
Error: Not equal:
expected: "\\.ssh/(?-m:$)"
actual : "(?-m:\\.ssh/$)"
Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-\.ssh/(?-m:$)
+(?-m:\.ssh/$)
Test: TestConfig
```

Contributor guide

Open the contributing guide

Research direction

Start in auditbeat/module/file_integrity/config_test.go at TestConfig, especially lines 57-60, and compare the expected regex strings with the Windows/Go 1.22 actual output. Run the test in the reported Windows 2022 and Go 1.22 environment; done means TestConfig passes with expectations that match the intended regex representation.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
testing-qa
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.