Flaky go.etcd.io/etcd/server/v3/etcdserver/api/v3compactor: TestPeriodicHourly

[ahrtr]

Which Github Action / Prow Jobs are flaking?

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/etcd-io_etcd/19426/pull-etcd-coverage-report/1895067242123497472

{Failed  === RUN   TestPeriodicHourly
    logger.go:146: 2025-02-27T11:08:18.530Z	INFO	starting auto periodic compaction	{"revision": 1, "compact-period": "2h0m0s"}
    logger.go:146: 2025-02-27T11:08:18.530Z	INFO	completed auto periodic compaction	{"revision": 1, "compact-period": "2h0m0s", "took": "0s"}
    logger.go:146: 2025-02-27T11:08:18.850Z	INFO	starting auto periodic compaction	{"revision": 10, "compact-period": "2h0m0s"}
    logger.go:146: 2025-02-27T11:08:18.851Z	INFO	completed auto periodic compaction	{"revision": 10, "compact-period": "2h0m0s", "took": "0s"}
    logger.go:146: 2025-02-27T11:08:19.032Z	INFO	starting auto periodic compaction	{"revision": 20, "compact-period": "2h0m0s"}
    logger.go:146: 2025-02-27T11:08:19.032Z	INFO	completed auto periodic compaction	{"revision": 20, "compact-period": "2h0m0s", "took": "0s"}
    logger.go:146: 2025-02-27T11:08:19.281Z	INFO	starting auto periodic compaction	{"revision": 30, "compact-period": "2h0m0s"}
    periodic_test.go:72: len(actions) = 0, expected >= 1
--- FAIL: TestPeriodicHourly (1.49s)
}

FYI. Previously I raised a similar issue #17054, which was resolved in #18608. It seems the fix still has flaw.

Which tests are flaking?

.

Github Action / Prow Job link

No response

Reason for failure (if possible)

No response

Anything else we need to know?

No response

[ivanvc]

Discussed during the biweekly triage meeting. Open to a contributor that can help verify the flake using stress. Then, we also want the fix for the flake.

https://github.com/etcd-io/etcd/blob/05d57531e44a398463f929248a8427ea3a295dbe/CONTRIBUTING.md#check-for-flaky-tests

[joshjms]

/assign

[joshjms]

/unassign

I don't think I have the necessary skills to fix this (I tried for the past week with no results). Would love to keep in touch with this issue and whoever will take this up. Thanks!