Skip to content

fix: disable t.Parallel on TestPortForward #10449

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 1, 2023

Conversation

spikecurtis
Copy link
Contributor

I've said it before, I'll say it again: you can't create a timed context before calling t.Parallel() and then use it after.

Fixes flakes like https://github.com/coder/coder/actions/runs/6716682414/job/18253279157

I've chosen just to drop t.Parallel() entirely rather than create a second context after the parallel call, since the vast majority of the test time happens before where the parallel call was. It does all the tailnet setup before t.Parallel().
Leaving a call to t.Parallel() is a bug risk for future maintainers to come in and use the wrong context in the latter part of the test by accident.

Copy link
Contributor Author

Current dependencies on/for this PR:

This stack of pull requests is managed by Graphite.

@spikecurtis spikecurtis merged commit 94eb9b8 into main Nov 1, 2023
@spikecurtis spikecurtis deleted the 11-01-fix_disable_t.Parallel_on_TestPortForward branch November 1, 2023 09:45
Copy link
Contributor Author

Merge activity

@github-actions github-actions bot locked and limited conversation to collaborators Nov 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants