From: Rémi Bernon rbernon@codeweavers.com
--- tools/gitlab/test.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/gitlab/test.yml b/tools/gitlab/test.yml index d2b1966ad6e..b08e7966bf8 100644 --- a/tools/gitlab/test.yml +++ b/tools/gitlab/test.yml @@ -42,7 +42,7 @@ - wine wineboot.exe -u - wineserver -w
-test-linux-32: +test-linux-64: extends: .wine-test variables: EXCLUDE_TESTS: "d3d10core:d3d10core d3d11:d3d11 d3d8:device d3d8:visual d3d9:d3d9ex d3d9:device d3d9:visual" @@ -52,7 +52,7 @@ test-linux-32: - job: build-linux script: - export WINETEST_COLOR=1 - - wine usr/local/lib/wine/i386-windows/winetest.exe -q -q -o - -t gitlab -u $CI_JOB_URL -n $EXCLUDE_TESTS + - wine usr/local/lib/wine/x86_64-windows/winetest.exe -q -q -o - -t gitlab -u $CI_JOB_URL -n $EXCLUDE_TESTS
debian-32: extends: .wine-test
Hi,
It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated.
The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details:
The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=125751
Your paranoid android.
=== debian11 (32 bit report) ===
wmvcore: wmvcore.c:1569: Test failed: Stream 0: Got hr 0xc00d0041.
Any reason not to do that?
Any reason not to do that?
I don't think we want to stop testing 32-bit, particularly with all the 32-on-64 work going on.
If the problem is that some tests are skipped on wow64, we can run these tests as 64-bit.