You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: This is probably a WSL issue rather than a cross issue; but I am reporting this here for any soul that comes across the same issue with a working workaround (so people can find it when searching for issues). Then crossposting this to WSL issues.
OS: Win11 build 22621 (also tested on 23475)
WSL (Latest):
On Windows, running Rust tests on a WSL based container (e.g. Docker+WSL2) or raw WSL leads to runtime errors; both on x86_64 and i686 targets. Appears to be an issue with test runner itself in this environment; the tested code has no effect on result.
Example:
Finished test [unoptimized + debuginfo] target(s) in
26.28s
Running unittests src/lib.rs (/target/x86_64-pc-win
dows-gnu/debug/deps/reloaded_memory_buffers-13b5df74e878
54aa.exe)
0044:err:winediag:nodrv_CreateWindow Application tried t
o create a window, but no driver could be loaded.
0044:err:winediag:nodrv_CreateWindow Make sure that your
X server is running and that $DISPLAY is set correctly.
0044:err:systray:initialize_systray Could not create tray window
00fc:err:virtual:virtual_setup_exception stack overflow 2704 bytes
in thread 00fc addr 0x170054b4a stack 0xed0570 (0xed0000-0xed1000-0
x10d0000)
Other Platforms/Backends
(for Reference)
Linux (Ubuntu VM):
Runs flawlessly.
Docker inside WSL
Running cross inside WSL exhibits the same behaviour as Windows+Docker:
You can work around this issue (for now) by being a rebel and doing the exact opposite:
(uncheck the box in Docker Desktop)
This should get tests successfully running under Wine:
What target(s) are you cross-compiling for?
x86_64-pc-windows-gnu
Which operating system is the host (e.g computer cross is on) running?
macOS
Windows
Linux / BSD
other OS (specify in description)
What architecture is the host?
x86_64 / AMD64
arm32
arm64 (including Mac M1)
What container engine is cross using?
docker
podman
other container engine (specify in description)
cross version
cross 0.2.5
Example
# Make sure you have Docker/Podman first
rustup target add x86_64-pc-windows-gnu
cross build --target x86_64-pc-windows-gnu
cross test --target x86_64-pc-windows-gnu
Additional information / notes
No response
The text was updated successfully, but these errors were encountered:
Checklist
Describe your issue
Note: This is probably a WSL issue rather than a
cross
issue; but I am reporting this here for any soul that comes across the same issue with a working workaround (so people can find it when searching for issues). Then crossposting this to WSL issues.OS: Win11 build
22621
(also tested on23475
)WSL (Latest):
On Windows, running Rust tests on a WSL based container (e.g. Docker+WSL2) or raw WSL leads to runtime errors; both on
x86_64
andi686
targets. Appears to be an issue with test runner itself in this environment; the tested code has no effect on result.Example:
Other Platforms/Backends
(for Reference)
Linux (Ubuntu VM):
Runs flawlessly.
Docker inside WSL
Running
cross
inside WSL exhibits the same behaviour as Windows+Docker:Workaround:
Today, the Windows install instructions specifically instruct you to install Docker with WSL2 backend.
You can work around this issue (for now) by being a rebel and doing the exact opposite:
(uncheck the box in Docker Desktop)
This should get tests successfully running under Wine:
What target(s) are you cross-compiling for?
x86_64-pc-windows-gnu
Which operating system is the host (e.g computer cross is on) running?
What architecture is the host?
What container engine is cross using?
cross version
cross 0.2.5
Example
Additional information / notes
No response
The text was updated successfully, but these errors were encountered: