We just added a Linux ONE instance to Apache CouchDB's automatic CI worker set and it started running the full CI suite on the main branch alongside x86_64, arm64, ppc64le. s390x seems to experience random disk IO stalls which lead db tests failing.
s390x
Run status group 0 (all jobs):
WRITE: bw=18.6MiB/s (19.5MB/s), 18.6MiB/s-18.6MiB/s (19.5MB/s-19.5MB/s), io=3495MiB (3665MB), run=188338-188338msec
PowerPC:
Run status group 0 (all jobs):
WRITE: bw=1465MiB/s (1536MB/s), 1465MiB/s-1465MiB/s (1536MB/s-1536MB/s), io=87.7GiB (94.2GB), run=61325-61325msec
x86_64:
Run status group 0 (all jobs):
WRITE: bw=46.9MiB/s (49.2MB/s), 46.9MiB/s-46.9MiB/s (49.2MB/s-49.2MB/s), io=3968MiB (4161MB), run=84646-84646msec
We just added a Linux ONE instance to Apache CouchDB's automatic CI worker set and it started running the full CI suite on the
main
branch alongside x86_64, arm64, ppc64le. s390x seems to experience random disk IO stalls which lead db tests failing.We created an issue tracking flaky tests on s390x: https://github.com/apache/couchdb/issues/4521
Would be it possible to increase the disk IO or swap out for a faster disk.
A quick fio benchmark showed IO throughput is the lowest on s390x instance amongst all the other architecture CI worker we have: