Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Internal Tracking: GetProcAddress Windows API call fails when running multi-threaded tests #281

Open
pan93412 opened this issue Jan 20, 2023 · 1 comment
Open

Internal Tracking: GetProcAddress Windows API call fails when running multi-threaded tests #281

pan93412 opened this issue Jan 20, 2023 · 1 comment
Labels
bug Something isn't working lock:upstream

Comments

@pan93412
Copy link
Member

@pan93412 pan93412 changed the title Internal Tracking: Internal Tracking:GetProcAddress Windows API call fails when running multi-threaded tests Jan 20, 2023
@pan93412 pan93412 changed the title Internal Tracking:GetProcAddress Windows API call fails when running multi-threaded tests Internal Tracking: GetProcAddress Windows API call fails when running multi-threaded tests Jan 20, 2023
@pan93412 pan93412 added bug Something isn't working lock:upstream labels Jan 20, 2023
pan93412 added a commit that referenced this issue Jan 20, 2023
@pan93412
fix(ci): Workaround for #281
e6b3523
@sunshowers
Copy link

Hi, primary author of nextest here! You could potentially also look at turning on test groups to enable mutual exclusion: https://nexte.st/book/test-groups.html

(You can make it so that test groups are only enabled on Windows)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working lock:upstream
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sunshowers @pan93412