Arvados

402046b592d67f9fef97f7c71bae4e3f53ca6e6f

developer-run-tests: #4782

developer-run-tests: #4783

c03210c7f7b3fe7a2faacca010bc203b796da698

developer-run-tests: #4784

3.1.2~rc1-1¶

build-and-publish-rc-packages: #274

The test compute node in step 1 doesn't make sense for this release.

• Docker 28 is the latest version and we already have that pinned.
• The rest of the 3.1.x series is locked into CUDA 560 after #22792, it's not possible to upgrade that version.
• We currently have no way to test ROCm.

2d35008224383dfacfa6b5f7b104a4cf855f1426

developer-run-tests: #4787

developer-run-tests-doc-sdk-java-R: #2239

build-and-publish-rc-packages: #275

docker-jobs-image-release: #90

Step 10 (test-provision) is blocked by #22918#note-9.

test-provision: #1196

Brett Smith wrote in #note-35:

• Docker 28 is the latest version and we already have that pinned.

This was true on main but not true on 3.1-staging. I have rolled in #22693 so the compute node builds stay closer to what we test.

Per discussion at standup, we will forego CWL conformance testing because there are obstacles to actually testing the rc effectively, and since there are no direct sdk/cwl changes, the risk of regressions is minimal. We'll still test the usual workflows on pirca.

Manual testing:

• Confirmed rich text editor for collection descriptions
• Confirmed project selection popup, with expected default, when running a workflow
• Left a tab open on a gVCF workflow process almost the whole time it ran. No observed performance issues.

packer-build-compute-image: #333

CUDA workflow: pirca-xvhdp-46hou369cziwnj3

S3 workflow: pirca-xvhdp-v7r66mdy9s1fgtw

chr19 workflow: pirca-xvhdp-eg0f3jykdrzdsf7

2025-05-22T18:16:41.017380933Z crunch-run 3.1.2~rc2 (go1.23.6) started
2025-05-22T18:16:41.017659205Z crunch-run process has uid=0(root) gid=0(root) groups=0(root)
2025-05-22T18:16:45.868321892Z Using FUSE mount: /usr/bin/arv-mount 3.1.2rc2
2025-05-22T18:16:45.874423825Z Using container runtime: docker Engine 28.1.1, containerd 1.7.27, runc 1.2.5, docker-init 0.19.0
2025-05-22T18:16:45.874447682Z Executing container: pirca-dz642-wdnoo6bv71znx20
[…]
2025-05-22T18:17:04.848920369Z INFO /usr/lib/python3-arvados-cwl-runner/bin/arvados-cwl-runner 3.1.2rc2, arvados-python-client 3.1.2rc2, cwltool 3.1.20240508115724

This LGTM, this is approved for release.

To keep history in one place, can you move the "3.1.2 Test Workflows" (pirca-j7d0g-y5vw0vfu1s5zzft) project to be under "Release Tests" (pirca-j7d0g-p8ixho6k8y7yud5)?

3.1.2~rc3 including #22779. Limited scope since this only changes the service definition for a-d-c and nothing else, but do want to at least make sure it deploys correctly and doesn't obviously break anything.

build-and-publish-rc-packages: #276

docker-jobs-image-release: #91

test-provision: #1200

No new compute node since nothing on it would be directly affected

Quick test workflow: pirca-xvhdp-0gwx7bl1ej3hdqu - shows crunch-run 3.1.2~rc3. Also checked the dispatch logs and journal to make sure there were no hiccups deploying the new version.

Lucas manually tested the actual fix on tordo, see #22946#note-3.

build-publish-packages-python-ruby: #97

build-and-publish-rc-packages: #277 - Right now we can't even build arvados/build:ubuntu2004 because:

19.47 The following packages have unmet dependencies:
19.58  libpam0g-dev:arm64 : Depends: libpam0g:arm64 (= 1.3.1-5ubuntu4.7) but it is not going to be installed
19.58                       Depends: libc6-dev:arm64 but it is not going to be installed or
19.58                                libc-dev:arm64
19.67 E: Unable to correct problems, you have held broken packages.
ERROR: process "/bin/sh -c /usr/bin/apt-get update && /usr/bin/apt-get install -o APT::Immediate-Configure=0 -q -y libpam0g-dev:arm64" did not complete successfully: exit code: 100

build-publish-packages-testing-ubuntu2204: #28 - The error changed:

08:48:43 25.44 E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/g/glibc/libc6_2.35-0ubuntu3.10_amd64.deb  404  Not Found [IP: 91.189.91.81 80]
08:48:43 25.44 E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/g/glibc/libc-dev-bin_2.35-0ubuntu3.10_amd64.deb  404  Not Found [IP: 91.189.91.81 80]
08:48:43 25.44 E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/g/glibc/libc-devtools_2.35-0ubuntu3.10_amd64.deb  404  Not Found [IP: 91.189.91.81 80]
08:48:43 25.44 E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

It looks like they might be in the middle of some repository maintenance right now. Maybe related to the EOL of focal?

doc.arvados.org failed to update because the virtualenv for pdoc was still based on bookworm. Fortunately the deployment code has logic to rebuild the virtualenv. I moved the old one out of the way (to ~git/venv-pdoc.bullseye) and reran the build script and now we're good.

build-publish-packages-python-ruby: #97

build-and-publish-rc-packages: #283

docker-jobs-image-release: #92

publish-packages-to-stable-repo: #292

build-publish-packages-python-ruby: #98

build-java-sdk: #60

build-package-r: #40

build-and-release-docker-arvbox-demo-image: #65

Jenkins configuration:

• developer-run-tests 2024-11-18_18-23-36
• developer-run-tests-sdk-java-R 2025-04-03_18-21-26
• packer-build-jenkins-image-arvados-tests: #119 jenkins-image-arvados-tests-20250417181704