Skip to content

[v18] Rewrite notifications tests#59665

Merged
zmb3 merged 1 commit intobranch/v18from
bot/backport-59414-branch/v18
Nov 26, 2025
Merged

[v18] Rewrite notifications tests#59665
zmb3 merged 1 commit intobranch/v18from
bot/backport-59414-branch/v18

Conversation

@zmb3
Copy link
Copy Markdown
Collaborator

@zmb3 zmb3 commented Sep 26, 2025

Backport #59414 to branch/v18

@zmb3 zmb3 added the no-changelog Indicates that a PR does not require a changelog entry label Sep 26, 2025
@public-teleport-github-review-bot public-teleport-github-review-bot bot removed the request for review from rudream September 29, 2025 12:25
@zmb3
Copy link
Copy Markdown
Collaborator Author

zmb3 commented Sep 29, 2025

This is using the Go 1.25 synctest API, so it won't merge as-is.

I'll hold it open for a bit and if we continue to be disrupted by the flakiness on release branches I'll make it compatible with Go 1.24, otherwise we'll just have the new tests going forward on master.

@greedy52
Copy link
Copy Markdown
Contributor

This is using the Go 1.25 synctest API, so it won't merge as-is.

I'll hold it open for a bit and if we continue to be disrupted by the flakiness on release branches I'll make it compatible with Go 1.24, otherwise we'll just have the new tests going forward on master.

Is it possibles to upgrade to go 1.25 on v18? i started writing some tests in synctest as well that needs to be backported 😭

@tigrato
Copy link
Copy Markdown
Contributor

tigrato commented Sep 29, 2025

This is using the Go 1.25 synctest API, so it won't merge as-is.

I'll hold it open for a bit and if we continue to be disrupted by the flakiness on release branches I'll make it compatible with Go 1.24, otherwise we'll just have the new tests going forward on master.

Is it possibles to upgrade to go 1.25 on v18? i started writing some tests in synctest as well that needs to be backported 😭

We already have some tests using go 1.24 experimental synctest env var and build constrain

@greedy52
Copy link
Copy Markdown
Contributor

We already have some tests using go 1.24 experimental synctest env var and build constrain

i know. but we have manually move new tests to a different file and change synctest function .

TestNotifications has been flaky, and I suspect part of it is due
to the way we handle time. Notifications use UUIDv7, which include
a timestamp, so our tests were mixing a fake clock and a real clock.

This commit tests notifications using synctest without a fake clock
in sight.

Additionally, TestNotifications was testing too many things (pagination,
matching, RBAC, state mutation, etc). This commit breaks the test up
into several more-focused tests.

Updates #58392
@zmb3 zmb3 force-pushed the bot/backport-59414-branch/v18 branch from 4046a2e to a3cee56 Compare November 26, 2025 17:31
@zmb3 zmb3 enabled auto-merge November 26, 2025 17:34
@zmb3 zmb3 added this pull request to the merge queue Nov 26, 2025
Merged via the queue into branch/v18 with commit 9b79383 Nov 26, 2025
39 checks passed
@zmb3 zmb3 deleted the bot/backport-59414-branch/v18 branch November 26, 2025 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport no-changelog Indicates that a PR does not require a changelog entry size/sm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants