Fail when an EL section of packages-manifest.conf lacks uftp, which BUILD.md documents for every EL target. CI now compiles uftp/mockbuild.pl, parses uftp.spec and runs perlcritic on the builder. native/uftp-fixes.t builds the sender, the receiver and the proxy from the archive and the patches with AddressSanitizer, and gives the functions that handle each fixed message the message that broke them. It checks that each client list of the proxy fits in its packet buffer, and that the proxy forwards the NAKs of plain, TFMCC and short client STATUS messages in a whole NAK list. It sends the receiver files with short, repeated and lost blocks, file names that try to leave the destination directory, and names of that directory itself, then checks the files on disk. It also covers a file with more sections than the protocol holds, a seek of the sender past block 2^31, a group with more than 10000 entries, and the STATUS of the receiver for a full section. It ends a group after another group replaced its file or changed its path, and a restarted group after it changed the path of its unused file. It backs up files below a symbolic link in the backup directory, and along a backup path longer than 300 bytes. The built programs must carry the xCAT build mark. CI runs it with the native tests and installs the compiler and the OpenSSL headers for it.
1.1 KiB
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.