| Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
We want to eanble running tests as part of the build, but
our builds run in VMs with networking disabled.
|
|
We add a configure script for each subtest to add the required
qemu arguments.
Co-authored-by: Richard Maw <richard.maw@codethink.co.uk>
|
|
They always fail and do not ship with proper units so we can't
disable them with presets so we mask them instead.
|
|
These fail for unknown reasons on Ubuntu. Until someone from Ubuntu
who cares can figure out why, let's skip these tests on Ubuntu.
|
|
The timeout is reliably hit when running tests in mkosi.
|
|
|
|
On Debian/Ubuntu, the unit is named tgt.service instead of tgtd.service,
so let's make sure we take that into account.
On CentOS, tgtd.service is not available, so let's skip the test if we
can't find the service.
|
|
Otherwise we try to do the check before the udev queue is empty which
will make it fail.
|
|
The debian cloud kernel does not support ahci, so let's use
virtio-scsi-pci everywhere instead.
|
|
|
|
These are always aimed at the system image so ignore any specified
configure scripts in the minimal images.
|
|
Configuring extra cmdline arguments as a list is much nicer than
having to pass the --kernel-command-line-extra argument manually.
|
|
Most of these are identical, let's just generate from a meson
template.
|
|
Let's remove the unneeded NotifyAccess=all and start the socket
and service in the test itself instead of via the service unit. This
makes the test unit identical to the other test units which will allow
us to autogenerate it in a later commit.
|
|
Let's ship a .autorelabel file so we can get rid of
firstboot-autorelabel.service.
|
|
|
|
This allows doing other stuff with the test without actually defining
the test, such as generating a service unit automatically.
|
|
|
|
Having these named differently than the test itself mostly creates
unecessary confusion and makes writing logic against the tests harder
so let's rename the testsuite-xx units and scripts to just use the
test name itself.
|
|
Let's make this behave more like all the rest of the meson stuff.
This also is the first step to making it a bit more flexible so we
can define integration tests in different ways as will be seen in
the next commits.
|
|
We don't support this for any other tests either so let's drop the
support for running TEST-01-BASIC without installing as well to make
the upcoming commit easier to implement.
|
|
|
|
Currently, on soft-reboot, /run/credentials/@system is unmounted
because it has DefaultDependencies=yes and as such will have
Conflicts=umount.target and Before=umount.target. Let's make sure
credential mounts survive soft-reboot by implying DefaultDependencies=no
for credential mounts.
|
|
|
|
|
|
|
|
Also, do not bump 'line' until the end of the loop.
Otherwise, log_syntax() below logs about the wrong
line number.
|
|
|
|
The test-event test seems to be taking quite a bit more time than
the other 'simple tests', which usually complete in < 1s. In case
of a slower or loaded machine the default 30s timeout is not enough.
|
|
Follow-up for 7df0297ac5aa784209d4c719c87fdd707a9f34cf.
|
|
Follow-up for 2f6bd11c1a0147f6bd24bce3ed00c3d91c0884e6.
|
|
Follow-up for 84bdf71592be032fa4100fb7b0ed0a9345942ece.
|
|
Follow-up for 706ca67d3074b2a405ee8fe5de307416e4915b9f
|
|
|
|
[v6LC.3.2.2]
RFC 4862 Section 5.5.3, bullet e, sub-bullet 3 applies to existing
addresses, i.e. when address_get() returns success. If the address is
new (i.e. address_get() fails), then we should not be adding 2 hours to
the lifetime_valid_usec. Instead, use the valid_lifetime from the RA's
Prefix Information Option.
This change allows v6LC.3.2.2 to pass. Also verified all v6LC3.2.* tests
pass. This covers all the v6LC tests from Group2: Router Advertisement
Processing and Address Lifetime.
Fixes #32652.
|
|
[v6LC.2.2.15] (#32792)
Previously, RA option fields were being ignored when the Router Lifetime
value was zero. Remove this logic to be compliant with RFC4861.
Extract from: https://www.ietf.org/rfc/rfc4861.html#section-4.2, p.21,
first paragraph:
The Router Lifetime applies only to
the router's usefulness as a default router; it
does not apply to information contained in other
message fields or options.
This affected IPv6 Conformance test:
v6LC.2.2.15: Router Advertisement Processing, Reachable Time.
Fixes #31842.
Co-authored-by: Matt Muggeridge <Matt.Muggeridge@hpe.com>
|
|
destroy a curl context on exit
If we destroy both an event loop and a curl contect object at the same
time, then we get into this weird situation where curl wants us to
reconfigure a timout event source right before destruction, which
sd-event will refuse however, since it is already being shutdown.
Hence, catch that and simply don't bother adjusting the timeout, since
we cannot get back from there anyway.
|
|
name twice
|
|
This already gets reset in service_enter_dead()
and service_start().
|
|
|
|
buttons and axis (#32775)
The function `builtin-input_id` incorrectly identifies the ASRock LED Controller
as an input device due to the presence of buttons and axis. To fix this we add
a new rule in `hwdb.d/60-input-id.hwdb`.
The properties have been set to empty instead of `0` because some programs
might check if the value is set at all instead of checking its value, as discussed
in #32773.
The device has no real keys. The devices is controlled by i2c interface and some
settings in UEFI, and it provides an header to connect LED strips and similar devices.
I suppose it's possible that ASRock intended to connect devices with buttons for
controlling LEDs to it, but: (i) the controller itself does not have key, (ii) to my
knowledge no such device exists. So I think we can unset that property as well.
On a sidenote, unsetting those properties does not affect the i2c interface,
OpenRGB still interacts normally with the device.
Fixes #32773.
|
|
The state might be "freezing-by-parent" as well so let's take that
into account.
Fixes #32746
|
|
This is for making CIs for #32775 green.
|
|
Bumps pkg/arch from `b13e94a` to `b578e90`.
---
updated-dependencies:
- dependency-name: pkg/arch
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Bumps pkg/debian from `7cc898c` to `824c52f`.
---
updated-dependencies:
- dependency-name: pkg/debian
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
Even though v256-final is not released yet, let's v257 tag now to make
not PRs for v257 conflict with each other.
|
|
with OrderedHashmap
No functional change, just refactoring.
|
|
|
