This is an automated email from the ASF dual-hosted git repository.

nickva pushed a commit to branch jenkins-enable-ppc64le-and-s390x
in repository https://gitbox.apache.org/repos/asf/couchdb.git

commit 2a3e761c8c587b44b6b7321c5d5ddf5be169463a
Author: Nick Vatamaniuc <[email protected]>
AuthorDate: Wed Jul 15 12:06:31 2026 -0400

    Try to re-enable s390x and ppc64le
    
    Previous failures were often from picking up ASF Jenkins generic workers 
with
    `s390x` and `ppc64le` labels. Those workers were often over-subscribed and
    pretty flaky. To avoid that use different label that only our project would
    match.
---
 build-aux/Jenkinsfile | 53 ++++++++++++++++++++++++++-------------------------
 1 file changed, 27 insertions(+), 26 deletions(-)

diff --git a/build-aux/Jenkinsfile b/build-aux/Jenkinsfile
index 3406fe0c7..40080ace3 100644
--- a/build-aux/Jenkinsfile
+++ b/build-aux/Jenkinsfile
@@ -126,35 +126,36 @@ meta = [
   // agents at a time and often time out even with retries. The build times
   // take close to an hour, which is at least x2 as long as it takes to run
   // other arch CI jobs and they still time out often and fail. Disable for
-  // now. This is a low demand arch distro, maybe remove support altogether?
+  // now. That's why we have the ppc64le_own label and not ppc64le.
   //
-  // 'base-ppc64': [
-  //   name: 'Debian POWER',
-  //   spidermonkey_vsn: '78',
-  //   with_nouveau: true,
-  //   with_clouseau: true,
-  //   quickjs_test262: true,
-  //   image: "${DOCKER_IMAGE_BASE}-${ERLANG_VERSION}",
-  //   node_label: 'ppc64le',
-  //   gnu_make_eunit_opts: "${DEFAULT_GNU_MAKE_EUNIT_OPTS}"
-  // ],
+  'base-ppc64': [
+    name: 'Debian POWER',
+    spidermonkey_vsn: '78',
+    with_nouveau: true,
+    with_clouseau: true,
+    quickjs_test262: true,
+    image: "${DOCKER_IMAGE_BASE}-${ERLANG_VERSION}",
+    node_label: 'ppc64le_own',
+    gnu_make_eunit_opts: "${DEFAULT_GNU_MAKE_EUNIT_OPTS}"
+  ],
 
-  // Just like in the ppc64le case we sometimes "pick up" built-in s390x 
workers added to
-  // our jenkins, but since those are managed by us, our .mix/.venv/.hex 
packaging
-  // cache hack in /home/jenkins doesn't work, and so elixir tests fail. Skip 
this arch build
-  // until we figure out caching (probably need to use a proper caching 
plugin).
+  // Just like in the ppc64le case we sometimes "pick up" built-in s390x
+  // workers added to our jenkins, but since those are managed by us, our
+  // .mix/.venv/.hex packaging cache hack in /home/jenkins doesn't work, and so
+  // elixir tests fail. That's why we're using the s390x_own label instead of
+  // s390x
   //
-  // 'base-s390x': [
-  //   name: 'Debian s390x',
-  //   spidermonkey_vsn: '78',
-  //   with_nouveau: true,
-  //   // QuickJS test262 shows a discrepancy 
typedarray-arg-set-values-same-buffer-other-type.js
-  //   // Test262Error: 51539607552,42,0,4,5,6,7,8
-  //   quickjs_test262: false,
-  //   image: "${DOCKER_IMAGE_BASE}-${ERLANG_VERSION}",
-  //   node_label: 's390x',
-  //   gnu_make_eunit_opts: "${DEFAULT_GNU_MAKE_EUNIT_OPTS}"
-  // ],
+  'base-s390x': [
+    name: 'Debian s390x',
+    spidermonkey_vsn: '78',
+    with_nouveau: true,
+    // QuickJS test262 shows a discrepancy 
typedarray-arg-set-values-same-buffer-other-type.js
+    // Test262Error: 51539607552,42,0,4,5,6,7,8
+    quickjs_test262: false,
+    image: "${DOCKER_IMAGE_BASE}-${ERLANG_VERSION}",
+    node_label: 's390x_own',
+    gnu_make_eunit_opts: "${DEFAULT_GNU_MAKE_EUNIT_OPTS}"
+  ],
 
   'base': [
     name: 'Debian x86_64',

Reply via email to