From: Herton R. Krzesinski on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1526
Bugzilla: INTERNAL
The upstream and badfuncs tests reports some "problems" right now in
RHEL and probably Fedora (which seems to share similar config for those
tests), thus tune them for ark/Fedora.
Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com>
---
redhat/rpminspect.yaml | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
From: David Arcari <darcari(a)redhat.com>
move CONFIG_STRICT_SIGALTSTACK_SIZE to the appropriate directory
STRICT_SIGALTSTACK_SIZE is only present in arch/x86
Signed-off-by: David Arcari <darcari(a)redhat.com>
diff --git a/redhat/configs/common/generic/CONFIG_STRICT_SIGALTSTACK_SIZE b/redhat/configs/common/generic/x86/x86_64/CONFIG_STRICT_SIGALTSTACK_SIZE
rename from redhat/configs/common/generic/CONFIG_STRICT_SIGALTSTACK_SIZE
rename to redhat/configs/common/generic/x86/x86_64/CONFIG_STRICT_SIGALTSTACK_SIZE
index blahblah..blahblah 100644
--- a/redhat/configs/common/generic/CONFIG_STRICT_SIGALTSTACK_SIZE
+++ b/redhat/configs/common/generic/x86/x86_64/CONFIG_STRICT_SIGALTSTACK_SIZE
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1507
From: Herton R. Krzesinski <herton(a)redhat.com>
redhat: switch the vsyscall config to CONFIG_LEGACY_VSYSCALL_XONLY=y
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1876977
As discussed upstream eg. at https://lore.kernel.org/linux-api/87h7bzjaer.fsf@oldenburg.str.redhat.com/T/
and pointed on the bug's description above, VSYSCALL_XONLY is more
secure while still maintaining useful backward compatibility.
We also plan to do this change on the RHEL side with a centos-stream-9
change, so the change here covers both Fedora and RHEL/CentOS.
v2: move the CONFIG_LEGACY_VSYSCALL* files to the x86 directory, as they
are x86 only settings, as reported/suggested by Waiman Long.
Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com>
diff --git a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_EMULATE b/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_EMULATE
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_EMULATE
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_LEGACY_VSYSCALL_EMULATE=y
diff --git a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_XONLY b/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_XONLY
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_XONLY
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_LEGACY_VSYSCALL_XONLY is not set
diff --git a/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_EMULATE b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_EMULATE
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_EMULATE
@@ -0,0 +1 @@
+# CONFIG_LEGACY_VSYSCALL_EMULATE is not set
diff --git a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_NONE b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_NONE
rename from redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_NONE
rename to redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_NONE
index blahblah..blahblah 100644
--- a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_NONE
+++ b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_NONE
diff --git a/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_XONLY b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_XONLY
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_XONLY
@@ -0,0 +1 @@
+CONFIG_LEGACY_VSYSCALL_XONLY=y
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1531
From: Justin M. Forbes <jforbes(a)fedoraproject.org>
Turn CONFIG_DEVMEM back on for aarch64
We have ended up with a config mismatch for the RHEL configs in a way
that was unclear and untracked. CONFIG_STRICT_DEVMEM is enabled in
configs/common/generic, but CONFIG_DEVMEM was disabled for aarc64 in
RHEL (though not in Fedora). This creates a mismatch situation where the
configs do not get generated in the way they are set. Our options are
to either turn on CONFIG_DEVMEM as I have here, or turn off
CONFIG_STRICT_DEVMEM for aarch64. I went with the former, but I am
happy to change this if needed, we just need the configs coherent.
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
diff --git a/redhat/configs/ark/debug/arm/aarch64/CONFIG_DEVMEM b/redhat/configs/ark/debug/arm/aarch64/CONFIG_DEVMEM
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/ark/debug/arm/aarch64/CONFIG_DEVMEM
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_DEVMEM=y
diff --git a/redhat/configs/ark/generic/arm/aarch64/CONFIG_DEVMEM b/redhat/configs/ark/generic/arm/aarch64/CONFIG_DEVMEM
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/ark/generic/arm/aarch64/CONFIG_DEVMEM
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_DEVMEM is not set
diff --git a/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_DEVMEM b/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_DEVMEM
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_DEVMEM
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_DEVMEM=y
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1408
From: Rafael Aquini <aquini(a)redhat.com>
redhat: configs: increase CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE
Some really large instances do require a slightly increased pool size
so kmemleak can track early system allocations before kmemleak_object
entries can be allocated out of the system's slab caches. If there is
not enough entries in the pre-allocated static pool, the facility is
disabled at boot time and no futher tracking is done by kmemleak at
system's runtime (see RHBZ#2008118).
This patch doubles the size of kmemleak's memory pool size which for
now will allow enough room for proper kmemleak initialization for the
large systems described at RHBZ#2008118. Kernel memory footprint for
the kmemleak pool will increase from its current 7.17 mB to 14.34 mb.
Signed-off-by: Rafael Aquini <aquini(a)redhat.com>
diff --git a/redhat/configs/ark/debug/CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE b/redhat/configs/ark/debug/CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE
index blahblah..blahblah 100644
--- a/redhat/configs/ark/debug/CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE
+++ b/redhat/configs/ark/debug/CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE
@@ -1 +1 @@
-CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE=20000
+CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE=40000
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1516
From: Jeremy Linton on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1393
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2007430
Upstream Status: RHEL-only
Windows on Arm is a thing, and some of those machines support
HYPERV. For WoA users it would be helpful if Fedora/etc
ran well as a guest OS.
Signed-off-by: Jeremy Linton <jlinton(a)redhat.com>
---
arch/arm64/hyperv/mshyperv.c | 18 +++++++--
arch/arm64/include/asm/mshyperv.h | 18 ++++++++++
arch/arm64/kernel/setup.c | 4 ++
drivers/clocksource/hyperv_timer.c | 14 +++++++
drivers/hv/Kconfig | 2 +-
redhat/configs/ark/generic/arm/aarch64/CONFIG_INPUT_KEYBOARD | 1 -
redhat/configs/common/generic/arm/aarch64/CONFIG_KEYBOARD_ATKBD | 1 +
redhat/configs/common/generic/arm/aarch64/CONFIG_SERIO_LIBPS2 | 1 +
redhat/configs/fedora/generic/arm/CONFIG_INPUT_MATRIXKMAP => redhat/configs/common/generic/arm/CONFIG_INPUT_MATRIXKMAP | 0
redhat/configs/fedora/generic/arm/CONFIG_KEYBOARD_TEGRA => redhat/configs/common/generic/arm/CONFIG_KEYBOARD_TEGRA | 0
10 files changed, 52 insertions(+), 7 deletions(-)
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.15.12-100.fc34
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=80607160
The results of these automated tests are provided below.
Overall result: PASSED
Tests: OK
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?prefi…
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
Host 1:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ Reboot test
🚧 ⚡⚡⚡ Storage blktests - srp
Host 2:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
✅ Boot test
✅ Reboot test
✅ ACPI table test
⚡⚡⚡ LTP - cve
⚡⚡⚡ LTP - sched
⚡⚡⚡ LTP - syscalls
⚡⚡⚡ LTP - can
⚡⚡⚡ LTP - commands
⚡⚡⚡ LTP - containers
⚡⚡⚡ LTP - dio
⚡⚡⚡ LTP - fs
⚡⚡⚡ LTP - fsx
⚡⚡⚡ LTP - math
⚡⚡⚡ LTP - hugetlb
⚡⚡⚡ LTP - mm
⚡⚡⚡ LTP - nptl
⚡⚡⚡ LTP - pty
⚡⚡⚡ LTP - ipc
⚡⚡⚡ LTP - tracing
⚡⚡⚡ LTP: openposix test suite
⚡⚡⚡ CIFS Connectathon
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Ethernet drivers sanity
🚧 ⚡⚡⚡ xarray-idr-radixtree-test
🚧 ⚡⚡⚡ NFS Connectathon
Host 3:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ Reboot test
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ Storage blktests - blk
🚧 ⚡⚡⚡ Storage blktests - nvme-tcp
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ stress: stress-ng - interrupt
🚧 ⚡⚡⚡ stress: stress-ng - cpu
🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache
🚧 ⚡⚡⚡ stress: stress-ng - memory
🚧 ⚡⚡⚡ stress: stress-ng - os
Host 4:
✅ Boot test
✅ Reboot test
✅ Ethernet drivers sanity - mlx5
Host 5:
✅ Boot test
✅ Reboot test
🚧 ✅ Storage blktests - nvmeof-mp
Host 6:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ Reboot test
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ Storage blktests - blk
🚧 ⚡⚡⚡ Storage blktests - nvme-tcp
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ stress: stress-ng - interrupt
🚧 ⚡⚡⚡ stress: stress-ng - cpu
🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache
🚧 ⚡⚡⚡ stress: stress-ng - memory
🚧 ⚡⚡⚡ stress: stress-ng - os
Host 7:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ Reboot test
🚧 ⚡⚡⚡ Storage blktests - srp
ppc64le:
Host 1:
✅ Boot test
✅ Reboot test
✅ LTP - cve
✅ LTP - sched
✅ LTP - syscalls
✅ LTP - can
✅ LTP - commands
✅ LTP - containers
✅ LTP - dio
✅ LTP - fs
✅ LTP - fsx
✅ LTP - math
✅ LTP - hugetlb
✅ LTP - mm
✅ LTP - nptl
✅ LTP - pty
✅ LTP - ipc
✅ LTP - tracing
✅ LTP: openposix test suite
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ xarray-idr-radixtree-test
🚧 ✅ NFS Connectathon
Host 2:
✅ Boot test
✅ Reboot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ Storage: swraid mdadm raid_module test
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests - blk
🚧 ✅ Storage blktests - nvme-tcp
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage: lvm device-mapper test - upstream
🚧 ✅ storage: software RAID testing
Host 3:
✅ Boot test
✅ Reboot test
🚧 ❌ Storage blktests - srp
Host 4:
✅ Boot test
✅ Reboot test
🚧 ✅ Storage blktests - nvmeof-mp
s390x:
Host 1:
✅ Boot test
✅ Reboot test
✅ Storage: swraid mdadm raid_module test
🚧 ✅ Storage blktests - blk
🚧 ✅ Storage blktests - nvme-tcp
🚧 ✅ stress: stress-ng - interrupt
🚧 ✅ stress: stress-ng - cpu
🚧 ✅ stress: stress-ng - cpu-cache
🚧 ✅ stress: stress-ng - memory
🚧 ✅ stress: stress-ng - os
Host 2:
✅ Boot test
✅ Reboot test
✅ LTP - cve
✅ LTP - sched
✅ LTP - syscalls
✅ LTP - can
✅ LTP - commands
✅ LTP - containers
✅ LTP - dio
✅ LTP - fs
✅ LTP - fsx
✅ LTP - math
✅ LTP - hugetlb
✅ LTP - mm
✅ LTP - nptl
✅ LTP - pty
✅ LTP - ipc
✅ LTP - tracing
✅ LTP: openposix test suite
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ❌ xarray-idr-radixtree-test
🚧 ✅ NFS Connectathon
Host 3:
✅ Boot test
✅ Reboot test
🚧 ✅ Storage blktests - nvmeof-mp
Host 4:
✅ Boot test
✅ Reboot test
🚧 ✅ Storage blktests - srp
x86_64:
Host 1:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
✅ Boot test
✅ Reboot test
✅ ACPI table test
✅ LTP - cve
✅ LTP - sched
✅ LTP - syscalls
✅ LTP - can
✅ LTP - commands
✅ LTP - containers
⚡⚡⚡ LTP - dio
⚡⚡⚡ LTP - fs
⚡⚡⚡ LTP - fsx
⚡⚡⚡ LTP - math
⚡⚡⚡ LTP - hugetlb
⚡⚡⚡ LTP - mm
⚡⚡⚡ LTP - nptl
⚡⚡⚡ LTP - pty
⚡⚡⚡ LTP - ipc
⚡⚡⚡ LTP - tracing
⚡⚡⚡ LTP: openposix test suite
⚡⚡⚡ CIFS Connectathon
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Ethernet drivers sanity
🚧 ⚡⚡⚡ xarray-idr-radixtree-test
🚧 ⚡⚡⚡ NFS Connectathon
Host 2:
✅ Boot test
✅ Reboot test
🚧 ✅ Storage blktests - srp
Host 3:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ Reboot test
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
⚡⚡⚡ xfstests - nfsv4.2
⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ xfstests - cifsv3.11
🚧 ⚡⚡⚡ Storage blktests - blk
🚧 ⚡⚡⚡ Storage blktests - nvme-tcp
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream
🚧 ⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ stress: stress-ng - interrupt
🚧 ⚡⚡⚡ stress: stress-ng - cpu
🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache
🚧 ⚡⚡⚡ stress: stress-ng - memory
🚧 ⚡⚡⚡ stress: stress-ng - os
Host 4:
✅ Boot test
✅ Reboot test
🚧 ✅ Storage blktests - nvmeof-mp
Host 5:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ Reboot test
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
⚡⚡⚡ xfstests - nfsv4.2
⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ xfstests - cifsv3.11
🚧 ⚡⚡⚡ Storage blktests - blk
🚧 ⚡⚡⚡ Storage blktests - nvme-tcp
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream
🚧 ⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ stress: stress-ng - interrupt
🚧 ⚡⚡⚡ stress: stress-ng - cpu
🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache
🚧 ⚡⚡⚡ stress: stress-ng - memory
🚧 ⚡⚡⚡ stress: stress-ng - os
Host 6:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ Reboot test
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
⚡⚡⚡ xfstests - nfsv4.2
⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ xfstests - cifsv3.11
🚧 ⚡⚡⚡ Storage blktests - blk
🚧 ⚡⚡⚡ Storage blktests - nvme-tcp
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream
🚧 ⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ stress: stress-ng - interrupt
🚧 ⚡⚡⚡ stress: stress-ng - cpu
🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache
🚧 ⚡⚡⚡ stress: stress-ng - memory
🚧 ⚡⚡⚡ stress: stress-ng - os
Test sources: https://gitlab.com/cki-project/kernel-tests
💚 Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with ⚡⚡⚡.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with 🚧. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with ⏱.