[tests-only][full-ci] Run oc10 tests in github

[PrajwolAmatya]

Description

Run GUI tests with oc10.

Related issue:

• [QA] [Desktop] migrate GUI tests from drone to GitHub #12258

[PrajwolAmatya]

CI is exiting with error:

Error: Process completed with exit code 137.

https://github.com/owncloud/client/actions/runs/25777451084/job/75712933328?pr=12424

[DeepDiver1975]

Root Cause Analysis: Exit Code 137 in "Install Python modules"

What exit code 137 means

Exit code 137 = 128 + SIGKILL (9). This is the Linux OOM killer sending SIGKILL to a process because the system ran out of memory — not a normal process exit; the kernel forcibly killed it.

Exact failure sequence

Collecting PyGObject==3.42.*
  Downloading PyGObject-3.42.2.tar.gz (719 kB)     ← source tarball, no binary wheel
  Installing build dependencies: started             ← spawns sub-process for meson, pycairo, etc.
##[error]Process completed with exit code 137.      ← OOM kill ~2 seconds later

Root cause

PyGObject 3.42.x has no prebuilt binary wheel on PyPI for Linux/Fedora. pip must compile it from source. With build isolation (the default), pip:

1. Creates an isolated virtual environment
2. Spawns a sub-pip to install build dependencies (meson, pycairo, setuptools, …) into that env
3. Then runs the C compilation

Step 2 triggers a memory spike. The GitHub Actions ubuntu-latest runner has ~7 GB RAM, and at the point "Install Python modules" runs, all of the following are competing for that memory:

Container	Why it's running
squish	Running squish installation + executing pip inside it
owncloud (PHP 7.4 Apache)	Started and serving
mysql (service container)	Running
pip's isolated build env	Just spawned to install meson/pycairo build deps

The OOM killer fires ~2 seconds into "Installing build dependencies" and kills the pip process inside the squish container.

Why this job is particularly affected

The gui-tests-oc10 job (new in this PR) uses docker run -d --name squish ... plus a running owncloud container and mysql service — so all three are consuming memory simultaneously when pip tries to compile PyGObject. The prior gui-tests job ran squish natively via the container: directive with no additional containers, avoiding this memory pressure.

Fix options

Option 1 (recommended): install PyGObject as a system package via dnf before pip runs

- name: Install Python modules
  run: |
    docker exec squish bash -c "
      dnf install -y python3-gobject python3-gobject-devel &&
      make -C ${{ github.workspace }}/test/gui install
    "

This satisfies the PyGObject requirement without triggering a source compilation, so no memory spike.

Option 2: bake PyGObject into the squish image

Add python3-gobject to owncloudci/squish:fedora-42-* so it is already present and pip's source build never runs. Most robust long-term.

Option 3 (workaround): --no-build-isolation

Pre-install build deps with dnf, then pass --no-build-isolation to pip to avoid the isolated-env sub-process:

dnf install -y python3-gobject-devel gobject-introspection-devel cairo-gobject-devel meson
python3.10 -m pip install --no-build-isolation -r requirements.txt