Skip to content

Debian unstable memory debug#382

Draft
Agathe Porte (gagath) wants to merge 11 commits into
qualcomm-linux:mainfrom
gagath:debian-unstable-memory-debug
Draft

Debian unstable memory debug#382
Agathe Porte (gagath) wants to merge 11 commits into
qualcomm-linux:mainfrom
gagath:debian-unstable-memory-debug

Conversation

@gagath

Copy link
Copy Markdown
Contributor

Do not merge, for testing CI runners behavior only.

Loïc Minier (lool) and others added 10 commits April 24, 2026 14:28
Add $suite (default: "trixie") template variable to the rootfs recipe.
Use $suite in mmdebstrap's suite field instead of the previously
hardcoded value.

Signed-off-by: Loïc Minier <loic.minier@oss.qualcomm.com>
Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
Replace the static overlays/apt-sources/ overlay with a shell run action
that generates /etc/apt/sources.list.d/debian.sources based on the
$suite template variable.

Signed-off-by: Loïc Minier <loic.minier@oss.qualcomm.com>
Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
Replace the static overlays/backports/ overlay with a shell run action
that generates debian-backports.sources and debian-backports.pref using
the $suite variable.

Signed-off-by: Loïc Minier <loic.minier@oss.qualcomm.com>
Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
Remove the static .sources and .pref files from the qsc-deb-releases
overlay, keeping only the keyring (.asc). Add a run action that
generates them dynamically using $suite-overlay as the suite name.

Signed-off-by: Loïc Minier <loic.minier@oss.qualcomm.com>
Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
fastrpc-tests is only installed for trixie (only in trixie-overlay).

Signed-off-by: Loïc Minier <loic.minier@oss.qualcomm.com>
Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
Add suite inputs to the reusable debos workflow, with defaulting to
trixie. Use these for all debos invocations. Note that the container
image is still using trixie as forky currently leads to errors during
build (tracked in issue qualcomm-linux#379).

Update just the PR build workflow to use a matrix strategy building both
trixie and forky suites.

Take this opportunity to rename build-pr to just build.

Signed-off-by: Loïc Minier <loic.minier@oss.qualcomm.com>
Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
Create qsc-deb-releases .sources file with "Enabled: no" and only enable
it after verifying the suite exists via a wget probe of the Release
file.

Signed-off-by: Loïc Minier <loic.minier@oss.qualcomm.com>
Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
Prefix all published artifact filenames with "$suite-" so
that builds for different distributions/suites can coexist in the same
S3 destination:

- debos.yml: use prefix for image artifacts going to staging directory,
  including SBOMs
- lava-test.yml: add suite inputs and expose it as SUITE env var; add
  corresponding sed substitutions when rendering templates
- LAVA templates: reference {{SUITE}}-flash-*.tar.gz
- build-daily.yml, linux.yml: pass suite when calling lava-test.yml

Signed-off-by: Loïc Minier <loic.minier@oss.qualcomm.com>
Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
Our custom qcom1 kernel is not available for forky. Switch back to the
default Debian linux-image-arm64 kernel instead when building for forky.

Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
In order to prepare for using Debian forky as a build container that
seem to use more memory than trixie, increase default memory and
scratchsize.

Signed-off-by: Agathe Porte <agathe.porte@oss.qualcomm.com>
@gagath Agathe Porte (gagath) force-pushed the debian-unstable-memory-debug branch from a7987c8 to f3c0a39 Compare April 24, 2026 14:04
@gagath

Copy link
Copy Markdown
Contributor Author

Loïc Minier (@lool) this seems to be a runner OOM rather than a fakemachine OOM, so we have likely to bump the memory of the runners. I see three of them that can run the build-debos job:

    runs-on: [self-hosted, qcom-u2404, arm64]

Do you know the memory configuration of each runner, and if they can be upped somehow? Thanks.

@lool

Copy link
Copy Markdown
Contributor

Do you know the memory configuration of each runner, and if they can be upped somehow? Thanks.

I don't but I'll loop you in a thread where I'll ask!

@lool

Copy link
Copy Markdown
Contributor

Do you know the memory configuration of each runner, and if they can be upped somehow? Thanks.

I don't but I'll loop you in a thread where I'll ask!

  • vCPUs 16
  • Memory (GiB) 64

So probably not a limit of physical memory size :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants