This might be related to the same issue described in the previous
commit: Till we can update the container image to the Feb 11 security
update, x86 executables and in general the container image will behave
badly because of:
https://support.microsoft.com/en-us/help/4542617/you-might-encounter-issues-when-using-windows-server-containers-with-t
vs2017 x86 has been failing with a runner system failure while
uploading artifacts / submitting job status:
```
Uploading artifacts...
gst-build/build/meson-logs/: found 2 matching files
WARNING: Failed to load system CertPool: crypto/x509: system root pool is not available on Windows
ERROR: Job failed (system failure): aborted: <nil>
```
https://gitlab.freedesktop.org/slomo/gst-plugins-good/-/jobs/2084184
Disable it for now.
build vs2017 x86:
extends: '.build windows'
+ # Disabled until the container image can be updated
+ rules:
+ - allow_failure: true
+ when: 'manual'
variables:
ARCH: 'x86'
-# Disabled until the runner issues has been resolved.
build msys2 :
extends: '.build windows'
+ # Disabled until the container image can be updated
rules:
- - if: '$CI_PROJECT_NAME !~ /^(cerbero|gst-docs|gst-integration-testsuites|gst-omx|gst-plugins-rs|gstreamer-vaapi)$/'
- allow_failure: true
- when: manual
+ - allow_failure: true
+ when: 'manual'
timeout: '60min'
script:
# Sometimes there's seems to be an existing gst-build clone that comes either from the ether or