[PATCH 0/1] MR3361: gitlab: Skip amstream:amstream since it fails systematically.

[Francois Gouget (＠fgouget)]

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55283

---
It has been causing every merge request to get a GitLab CI error ever
since the move to Debian 12 on 2023-07-10. That makes the GitLab CI
pretty horrible.

If there is a quick fix for this issue then this MR can be ignored.
Otherwise, since there is no way to tell the GitLab CI that a specific
test is expected to crash or fail in a certain way, there is no other
option than to skip the test entirely until it works again.

Side-note: Finding failures in the GitLab CI logs is quite annoying. As
far as I can tell the only way not to miss any is to perform a set of
four searches:
- "Test f" -> regular failures
- "todo "  -> Todo tests that unexpectedly succeed
- "ne (2"  -> Timeouts (and test units with 2 failures)
- "ne (-"  -> Crashes (with or without an 'unhandled exception' line)

If anyone has an emacs macro to automate this...

[PATCH 1/1] gitlab: Skip amstream:amstream since it fails systematically.

[Francois Gouget]

From: Francois Gouget

Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=55283
---
It has been causing every merge request to get a GitLab CI error ever
since the move to Debian 12 on 2023-07-10. That makes the GitLab CI
pretty horrible.

If there is a quick fix for this issue then this MR can be ignored.
Otherwise, since there is no way to tell the GitLab CI that a specific
test is expected to crash or fail in a certain way, there is no other
option than to skip the test entirely until it works again.

Side-note: Finding failures in the GitLab CI logs is quite annoying. As
far as I can tell the only way not to miss any is to perform a set of
four searches:
  "Test f" -> regular failures
  "todo "  -> Todo tests that unexpectedly succeed
  "ne (2"  -> Timeouts (and test units with 2 failures)
  "ne (-"  -> Crashes (with or without an 'unhandled exception' line)
If anyone has an emacs macro to automate this...
---
 tools/gitlab/test.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/gitlab/test.yml b/tools/gitlab/test.yml
index 1fa0ce402af..9371cb182c5 100644
--- a/tools/gitlab/test.yml
+++ b/tools/gitlab/test.yml
@@ -57,7 +57,7 @@ test-linux-64:
 test-linux-32:
   extends: .wine-test
   variables:
-    EXCLUDE_TESTS: "d3d10core:d3d10core d3d11:d3d11 d3d8:device d3d8:visual d3d9:d3d9ex d3d9:device d3d9:visual"
+    EXCLUDE_TESTS: "amstream:amstream d3d10core:d3d10core d3d11:d3d11 d3d8:device d3d8:visual d3d9:d3d9ex d3d9:device d3d9:visual"
   rules:
     - if: $CI_PIPELINE_SOURCE == 'merge_request_event'
   needs:

[Zebediah Figura (＠zfigura)]

The backtrace says "wow64", does that mean new wow64 or old wow64?

[Alexandre Julliard (＠julliard)]

> The backtrace says "wow64", does that mean new wow64 or old wow64?

The gitlab CI is using old wow64.

[PATCH 0/1] MR3361: gitlab: Skip amstream:amstream since it fails systematically. - closed

[Francois Gouget (＠fgouget)]

This merge request was closed by Francois Gouget.