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!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
/etc/systemd/journald.conf.d drop-in dir already exists on SUSE.
(cherry picked from commit 56a894e888002f44f3463b3188f9d5abdcca4bb0)
(cherry picked from commit 10b7e0a0afc31dc6a3cc30fca3a276449a60ec7d)
(cherry picked from commit d0b9feab0158b57a3eff7becf9d35d07cb8cb20b)
(cherry picked from commit 58ff4df09596b725f7a654e427832e7d3829eec2)
The original way of appending to /etc/systemd/journald.conf doesn't work
anymore, since we no longer ship the default configs in /etc/.
(cherry picked from commit 1d556e9e2a01e538ecddd8a2d8fb843391caf410)
(cherry picked from commit cfe745d9850f2c199c97d789ca04e7f2e2d44d8d)
(cherry picked from commit e1f48e1aae2641b03718879a65ea6f5908b7be3c)
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)
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)
(The one case that is left unchanged is '< <(subcommand)'.)
This way, the style with no gap was already dominant. This way, the reader
immediately knows that ' < ' is a comparison operator and ' << ' is a shift.
In a few cases, replace custom EOF replacement by just EOF. There is no point
in using someting like "_EOL" unless "EOF" appears in the text.
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.
