Vinícius Ferrão
4e5c72bbb5
Every openEuler section of packages-manifest.conf must list uftp. The ppc64le section is no longer exempt from the package parity check with the EL10 ppc64le section, so its native input catalog must declare an owner for uftp. native/uftp-openeuler.t runs mockbuild-all.pl --dry-run and checks that an openEuler target plans the uftp builder in its own mock config, and only when its manifest section lists uftp. CI runs it with the other native tests.
Native packaging tests
The openEuler packaging tests build and sign RPMs or require Linux namespaces.
They run separately from prove -r t on a disposable host with the required
native tools:
prove -v native/*.t
uftp-fixes.t builds the UFTP programs from the archive and patches in uftp/
with AddressSanitizer. It needs a C compiler, make, patch and the OpenSSL
headers.
Use an ordinary user for RPM builds. openeuler-power-inputs.t exercises the
whole build owner only on POWER with native Mock; its RPM admission checks also
run on x86_64. When running that test as root, set XCAT_TEST_BUILD_USER to an
unprivileged account for the fixture builds.
The fixtures are command doubles at the downloader and Mock boundaries. The POWER Mock adapter uses the installed Python API directly to load generated configurations. It does not execute another Python interpreter.
The Mock configuration test loads the installed Python API from a checked-in fixture and is kept outside the unit run.
Inspect TAP skips: a successful exit does not qualify an unavailable native tool or architecture.