From e0eb758c43be20024aa0c6f5a7fbec769cd79f3a Mon Sep 17 00:00:00 2001 From: Mickael Bourgois Date: Wed, 1 Jul 2026 19:29:52 +0200 Subject: [PATCH] CLDSRV-992: Fix missing s3 logs artifact for S3C (backport of CLDSRV-942) The s3c-ft-tests job runs cloudserver from the plain image, whose CMD is `yarn start` with output left on the container's stdout, so cloudserver's log is never written to /artifacts and never uploaded. Every other functional job already uses the -testcoverage image, whose docker-test-with-coverage.sh runs `nyc yarn start > /artifacts/s3.log 2> /artifacts/s3-stderr.log`. CLDSRV-942 fixed this on development/9.2 and it reached 9.3, 9.4, 9.5 and hotfix/9.3.13, but never this branch. It matters here: CLDSRV-992 row F8's ServiceUnavailable on this branch could not be root-caused because nginx, sproxyd and bucketd all logged clean and cloudserver's own log did not exist. Backport of https://github.com/scality/cloudserver/pull/6216 Issue: CLDSRV-992 --- .github/workflows/tests.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/tests.yaml b/.github/workflows/tests.yaml index d930b04643..9f88c59811 100644 --- a/.github/workflows/tests.yaml +++ b/.github/workflows/tests.yaml @@ -489,7 +489,7 @@ jobs: S3DATA: scality S3METADATA: scality S3VAULT: scality - CLOUDSERVER_IMAGE: ghcr.io/${{ github.repository }}:${{ github.sha }} + CLOUDSERVER_IMAGE: ghcr.io/${{ github.repository }}:${{ github.sha }}-testcoverage MPU_TESTING: "yes" DEFAULT_BUCKET_KEY_FORMAT: ${{ matrix.vformat }} ENABLE_NULL_VERSION_COMPAT_MODE: ${{ matrix.enable-null-compat }}