(couchdb) branch jenkins-enable-ppc64le-and-s390x updated (3afb0932f -> 09c1d10f8)

[va...@apache.org]

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

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


 discard 3afb0932f Try to re-enable s390x and ppc64le
     new 09c1d10f8 Try to re-enable s390x and ppc64le

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (3afb0932f)
            \
             N -- N -- N   refs/heads/jenkins-enable-ppc64le-and-s390x (09c1d10f8)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:

(couchdb) 01/01: Try to re-enable s390x and ppc64le

[va...@apache.org]

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 09c1d10f865bab98bb72d8bd2048684f7c265f7f
Author: Nick Vatamaniuc <va...@gmail.com>
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.
    
    s390x seems to have a slower disk and times out on a disk heavy prop test, so
    let's bump the timeout value there a bit.
---
 build-aux/Jenkinsfile                           | 53 +++++++++++++------------
 src/couch/test/eunit/couch_cfile_prop_tests.erl |  2 +-
 2 files changed, 28 insertions(+), 27 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',
diff --git a/src/couch/test/eunit/couch_cfile_prop_tests.erl b/src/couch/test/eunit/couch_cfile_prop_tests.erl
index a2d954e5c..33b5aa80e 100644
--- a/src/couch/test/eunit/couch_cfile_prop_tests.erl
+++ b/src/couch/test/eunit/couch_cfile_prop_tests.erl
@@ -19,7 +19,7 @@
 -include_lib("kernel/include/file.hrl").
 
 property_test_() ->
-    ?EUNIT_QUICKCHECK(60, 25000).
+    ?EUNIT_QUICKCHECK(90, 25000).
 
 -define(SIZE_LIMIT, 5000).
 -define(CFILE_FD, cfile_fd).