Drop unit and system tests on amd64cross32

amd64cross32 jobs run a cross-compiled 32-bit BIND 9 on the 64-bit
platform. This approach brings no build issues, and it is a good way to
catch 32-bit issues in BIND 9 code-base and ensure cross-compilation
keeps working.

Unfortunately, running unit and system tests is a problem:

- #3269 - doth-ns1 frequently failed to start
- #3316 - quota_test sometimes fails to create new thread
- #3956 - tcp-ns1 sometimes fails to allocate memory

There's little value in running unit and system tests on the
amd64cross32 platform, and it only means the effort spent by QA by
looking into what turns out to be 32-bit limitations.

(cherry picked from commit f86d4f3bd8c5755dbc6d115e4a274e74c3bd856b)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 9b9c75239db464a017f72bb7e6aee7a2aa0fda0b..866ac54eead09b599af5f2c3c004a8837d71485c 100644 (file)
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -761,8 +761,8 @@ unit:gcc:bullseye:unstable:amd64:
     - job: gcc:bullseye:amd64
       artifacts: true
 
-# Jobs for cross-compiled GCC builds on Debian 11 "bullseye" (amd64) with
-# 32-bit libraries
+# Build job for cross-compiled GCC builds on 64-bit Debian 11 "bullseye"
+# (amd64) with 32-bit BIND 9.
 
 gcc:bullseye:amd64cross32:
   variables:
@@ -774,20 +774,6 @@ gcc:bullseye:amd64cross32:
   <<: *debian_bullseye_amd64cross32_image
   <<: *build_job
 
-system:gcc:bullseye:amd64cross32:
-  <<: *debian_bullseye_amd64cross32_image
-  <<: *system_test_job
-  needs:
-    - job: gcc:bullseye:amd64cross32
-      artifacts: true
-
-unit:gcc:bullseye:amd64cross32:
-  <<: *debian_bullseye_amd64cross32_image
-  <<: *unit_test_job
-  needs:
-    - job: gcc:bullseye:amd64cross32
-      artifacts: true
-
 # Jobs for scan-build builds on Debian 11 "bullseye" (amd64)
 
 .scan_build: &scan_build