| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Also adjust the mention of location of mkosi files,
follow-up for d55ad7fe96eb1edf438a7a41a465723bd29d4b10.
|
|
|
|
| |
This mirros what 0aff7b7584 did for docs/.
|
|
|
|
| |
See: https://github.com/marketplace/actions/super-linter
|
| |
|
|
|
|
| |
This reverts commit 8b036b223a40fac9e53189db05d3798ec11eb475.
|
|
|
|
| |
Allows to get coverage data on coveralls.io
|
|
|
|
| |
It's slow and unaffected by compiler/flags, so no point in repeating it
|
| |
|
|
|
|
|
|
| |
It seems some of the tests break network connectivity on the host,
as the code coverage upload fails to establish a connection.
Run them in a network namespace with 'unshare -n'.
|
|
|
|
|
|
|
|
|
|
| |
\#20629 moved the mkosi configs to mkosi.default.d/ so we were building
for the host distro (Ubuntu) in each CI configuration. To fix it, we
write the distro we want to test to a mkosi.default file and mkosi
will apply the other necessary configs automatically from mkosi.default.d/<distro>
This commit also removes unnecessary CLI options that are already handled
by the config files.
|
|
|
|
| |
Also, drop clang-10 builds to conserve resources.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current pattern '#' triggers on the openSUSE kernel version that is
printed early during boot when no actual prompt is ready
> [ 0.000000] Linux version 5.12.10-1-default (geeko@buildhost) (gcc (SUSE Linux) 11.1.1 20210510 [revision 23855a176609fe8dda6abaf2b21846b4517966eb], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.36.1.20210326-4) #1 SMP Fri Jun 11 05:05:06 UTC 2021 (b92eaf7)
Instead wait for pattern that: a) should have fewer false positives, b)
still be with working on distro shells:
openSUSE (red color)
^[[1m^[[31mimage:~ #^[[m^O
arch
[root@image ~]#
debian
root@image:~#
ubuntu
root@image:~#
fedora
[root@image ~]#
|
|
|
|
|
|
| |
The current boot test relies on terminal login, therefore network setup
inside image is unnecessary. This opens up possibility to test images
that don't support the network setup via veth devices.
|
|
|
|
|
| |
Use mkosi GH action that includes fixes for openSUSE builds. This
enables testing openSUSE builds in CI.
|
|
|
|
|
|
| |
The fix/workaround from #18851 should, hopefully, make this redundant.
This reverts commit 48a3cf58d5ad9cf2a4a4e6167171070b88c25369.
|
|\
| |
| | |
ci: work around #19442 to make CI happy again
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We use the `autologin` mkosi option (see
mkosi.default.d/10-systemd.conf), so the pexpect root login throws
a (harmless) error:
```
Arch Linux (built from systemd tree)
Kernel 5.4.0-1047-azure on an x86_64 (console)
image login: root (automatic login)
root
root
[root@image ~]# systemctl poweroff
root
-bash: root: command not found
[root@image ~]# systemctl poweroff
```
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Let's introduce a somewhat ugly workaround for #19442 and retry
the systemd-nspawn image boot test up to three times in case it dies
with the dissect timeout. Since this issue occurs only in the Arch job,
limit the workaround to this job only.
|
|/ |
|
| |
|
|
|
|
|
| |
Focal builds for gcc-11 are finally available, so let's put them into
some use.
|
| |
|
|
|
|
|
| |
Also, ask people to use a recent stable release and provide useful version information.
Inspired by #19118.
|
|
|
|
|
|
| |
Ubuntu's systemd-nspawn doesn't support faccessat2() syscall, which is
required, since current Arch's glibc implements faccessat() via
faccessat2().
|
|
|
|
| |
This reverts commit 67c972c610de61789d1b6560d28340f70d4b1196.
|
|
|
|
|
|
|
| |
This reverts commit c39e36203ff79a831c93dfb9380c967cd7fdbb99.
Now that meson-0.57.1 (where https://github.com/mesonbuild/meson/issues/8347
is fixed) is out it should be safe to keep rolling forward.
|
| |
|
|
|
|
|
|
| |
Prompted by:
* https://github.com/systemd/systemd/pull/18641#issuecomment-780371055
* https://github.com/systemd/systemd/issues/18639
|
|
|
|
|
|
|
|
| |
It seems there is another meson (0.57.0) regression preventing clang from
building systemd with --optimization=3 -Db_lto=true
By analogy with https://github.com/google/oss-fuzz/pull/5199 let's just switch
to 0.56.2 for the time being
|
|
|
|
|
| |
Apparently it's not obvious that logs are a good thing to provide, hence
let's explicitly ask for them.
|
|\
| |
| | |
ci: run build test with clang-12 as well
|
| |
| |
| |
| |
| | |
Ubuntu repositories for clang 12 are finally up, so let's use it
in our CI.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
glibc 2.33-3 shipped on 2021-02-06 breaks running Arch containers on
systems with older kernels (like Ubuntu Focal). Until the issue is
resolved, let's pin the Arch repositories to glibc 2.32-5 to mitigate
the annoying CI fails.
See: https://bugs.archlinux.org/task/69563
|
|/
|
|
|
|
| |
It happens too often that what people ask for already is implemented.
Let's help cut the noise a bit, and make people check things first
hopefully, and at least make it either for us to detect such cases.
|
|
|
|
| |
See: docs/HACKING.md
|
| |
|
| |
|
|
|
|
| |
It's just a follow-up to https://github.com/systemd/systemd/issues/16834
|
|
|
|
| |
Follow-up for 2d816c9804c1d565797faff85c0fdbfb15f1e9d5
|
|
|
|
| |
Fixes: #18238
|
|
|
|
| |
As wait-online is located under src/network.
|
| |
|
| |
|
|
|
|
| |
It actually didn't do anything, the issue was somewhere else.
|
| |
|
| |
|
| |
|