Skip to content

Conversation

@grooverdan
Copy link
Member

v3 is s a amd64v3 construction option made by Ubuntu in 25.10, and also 26.04. It cased MDEV-38398 that we'd like to see.

There is some space issues - https://github.com/MariaDB/buildbot/actions/runs/20983884237/job/60314128205?pr=886

So the build has been slimmed down to exclude unused items from previous builders.

The msan based on Debian 13 is still failing, however we're only using Debian 12 clang-20 MSAN at the moment so leaving this to fix another day.

Added the amd64v3-ubuntu-2604-deb-autobake-migration as a migration pool.

I may have went to far avoiding another build arg.

@grooverdan
Copy link
Member Author

not sure why this is trigging so many non-debian builds.

Happy to rework ARCH_VARIANT into a input if required.

Feedback on using amd64v3-ubuntu-2604-deb-autobake-migration highly appreciated.

@RazvanLiviuVarzaru
Copy link
Collaborator

not sure why this is trigging so many non-debian builds.

Happy to rework ARCH_VARIANT into a input if required.

Feedback on using amd64v3-ubuntu-2604-deb-autobake-migration highly appreciated.

The template is referenced in the above layer so this is why it executes all workflows...

worker_pool=DEFAULT_AMD64_WORKER_POOL,
),
deb_release_builder(
name="amd64v3-ubuntu-2604-deb-autobake-migration",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If I understand correctly, Ubuntu is being cautious about making v3 the default.
Will it become the default in the April 26.04 release, or is this primarily to help Ubuntu developers provide a v3-compiled MariaDB Server in their repositories?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, driven by the Ubuntu initiative. I'd word it was to get MariaDB developers providing a server codebase ready to be compiled with amd64v3. I haven't broached if we're going to be doing a v3 release, but it might be a bit of a short time to do so.

if: ${{ env.MAIN_BRANCH == 'false' }}
run: |
podman manifest create ${{ env.REPO }}:${{ env.IMG }}
variant_ver=
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better make variant an optional input

@grooverdan grooverdan force-pushed the MDBF-1156 branch 2 times, most recently from 04beab1 to 869e9f9 Compare January 15, 2026 09:42
LTS release as such contains 4 arches.

Also Ubuntu is performing amd64v3 builds
based on
https://discourse.ubuntu.com/t/introducing-architecture-variants-amd64v3-now-available-in-ubuntu-25-10/71312.
This has already thrown up errors on MDEV-38398.

To account for this, add a ubuntu:26.04v3 builder so
we've got something working for Ubuntu's release. Its
currently unclear if we'll be doing a v3 release.
…lang18-asan

Github action where running out of space.

https://github.com/MariaDB/buildbot/actions/runs/20983884237/job/60314128205?pr=886

The requirement for clang in the 24.04 is only for x86_64 for the 10.6
asan build. This isn't required on other architectures and there's no
need for a 22.04 clang either.

In 10.11+ branches the msan builder is used for ASAN.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants