Skip to content

CI failure on windows #6567

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

Closed
Darksonn opened this issue May 17, 2024 · 3 comments · Fixed by #6568
Closed

CI failure on windows #6567

Darksonn opened this issue May 17, 2024 · 3 comments · Fixed by #6568
Labels
A-ci Area: The continuous integration setup E-help-wanted Call for participation: Help is requested to fix this issue.

Comments

@Darksonn
Copy link
Contributor

Our windows builds that test all crates have started failing with the following error:

    Finished `test` profile [unoptimized + debuginfo] target(s) in 3m 14s
error: creating test list failed

Caused by:
  for `tokio-macros`, command `'D:\a\tokio\tokio\target\debug\deps\tokio_macros-2a8683d94d36d244.exe' --list --format terse` exited with code 0xc0000135: The specified module could not be found. (os error 126)
--- stdout:

--- stderr:

---

The error is happening consistently and will need to be fixed asap, as it is preventing us from merging PRs.

Any ideas?

@Darksonn Darksonn added E-help-wanted Call for participation: Help is requested to fix this issue. A-ci Area: The continuous integration setup labels May 17, 2024
@ChrisDenton
Copy link

This is just a drive-by comment but it looks like that error first occurred 2 days ago: https://github.com/tokio-rs/tokio/actions/runs/9100468527

"The specified module could not be found" usually means a DLL isn't found. If someone runs it locally then they may be able to get more information. Perhaps a directory isn't in PATH that should be?

@ChrisDenton
Copy link

Assuming it's not a tokio change that caused this then one thing that stands out is a recent rustup change: rust-lang/rustup#3703. It used to add the bin directory to PATH but no longer does so.

Someone could try setting RUSTUP_WINDOWS_PATH_ADD_BIN=1 in the environment to check.

@Darksonn
Copy link
Contributor Author

Thanks @ChrisDenton !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ci Area: The continuous integration setup E-help-wanted Call for participation: Help is requested to fix this issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants