IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
To avoid the "mountpoint is busy" error.
(cherry picked from commit d7c1df84d9e9da81889e44836b054a1af94620e5)
(cherry picked from commit d452dd7a3726ca1b0ca2a99478fe6449472317be)
The TEST-24 has been silently timing out for quite a while in the C8S
job, as the check_result_qemu() override lacked some error checks,
whoopsie.
(cherry picked from commit e6faf0ee22cb7a449f1462f5a032110b46be31d5)
(cherry picked from commit f2283f6c62e0358c029da308849564e744a73170)
As we use it for /var and with the default 100 MiB there's not enough
space for the journal.
(cherry picked from commit b7e913841b1136dc4f15415df27f95fe67923b08)
(cherry picked from commit 033d8ab57e9708205518f9495427a14f0e7df896)
Otherwise we'd miss coverage from TEST-{02,24,61}, since they don't go
through the "standard" `check_result_common` hook.
Follow-up to 7bf20e48bd7d641a39a14a7feb749b7e8b0fc0f6.
Specifying the test number manually is tedious and prone to errors (as
recently proven). Since we have all the necessary data to work out the
test number, let's do it automagically.
The logic to query test state was rather complex. I don't quite grok the point
of ret=$((ret+1))… But afaics, the precise result was always ignored by the
caller anyway.
Building custom images for each test takes a lot of time.
Build the default one, and if the test needs incompatible changes
just copy it and extend it instead.
When tests are executed serially (the default), it seems better to launch
the fairly generic test that runs the unittests early in the sequence.
Right now the tests are ordered based on when they were written, but
this doesn't make much sense.
