❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: b132b0a33a00 - [redhat] kernel-5.8.0-0.rc0.20200611gitb29482fde649.1
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=bpftool --with=selftests --with=kabidw_base --without=debug --without=ipaclones --without=perf --without=tools
3 years, 10 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: b264bfe4ddbc - [redhat] kernel-5.8.0-0.rc0.20200610git84fc461db99b.1
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=bpftool --with=selftests --with=kabidw_base --without=debug --without=ipaclones --without=perf --without=tools
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in drivers/mmc
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_MMC_SDHCI_OF_DWCMSHC:
This selects Synopsys DesignWare Cores Mobile Storage Controller
support.
If you have a controller with this interface, say Y or M here.
If unsure, say N.
Symbol: MMC_SDHCI_OF_DWCMSHC [=n]
Type : tristate
Defined at drivers/mmc/host/Kconfig:205
Prompt: SDHCI OF support for the Synopsys DWC MSHC
Depends on: MMC [=m] && MMC_SDHCI_PLTFM [=m] && OF [=y] && COMMON_CLK [=y]
Location:
-> Device Drivers
-> MMC/SD/SDIO card support (MMC [=m])
-> Secure Digital Host Controller Interface support (MMC_SDHCI [=m])
-> SDHCI platform and OF driver helper (MMC_SDHCI_PLTFM [=m])
---
Cc: Gopal Tiwari <gtiwari(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../generic/CONFIG_MMC_SDHCI_OF_DWCMSHC | 1 +
.../generic/CONFIG_MMC_SDHCI_OF_DWCMSHC | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_MMC_SDHCI_OF_DWCMSHC
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MMC_SDHCI_OF_DWCMSHC
diff --git a/redhat/configs/common/generic/CONFIG_MMC_SDHCI_OF_DWCMSHC b/redhat/configs/common/generic/CONFIG_MMC_SDHCI_OF_DWCMSHC
new file mode 100644
index 000000000000..a0ac36500753
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MMC_SDHCI_OF_DWCMSHC
@@ -0,0 +1 @@
+# CONFIG_MMC_SDHCI_OF_DWCMSHC is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_MMC_SDHCI_OF_DWCMSHC b/redhat/configs/pending-common/generic/CONFIG_MMC_SDHCI_OF_DWCMSHC
deleted file mode 100644
index 8a6cc248e652..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_MMC_SDHCI_OF_DWCMSHC
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_MMC_SDHCI_OF_DWCMSHC:
-#
-# This selects Synopsys DesignWare Cores Mobile Storage Controller
-# support.
-# If you have a controller with this interface, say Y or M here.
-# If unsure, say N.
-#
-# Symbol: MMC_SDHCI_OF_DWCMSHC [=n]
-# Type : tristate
-# Defined at drivers/mmc/host/Kconfig:205
-# Prompt: SDHCI OF support for the Synopsys DWC MSHC
-# Depends on: MMC [=m] && MMC_SDHCI_PLTFM [=m] && OF [=y] && COMMON_CLK [=y]
-# Location:
-# -> Device Drivers
-# -> MMC/SD/SDIO card support (MMC [=m])
-# -> Secure Digital Host Controller Interface support (MMC_SDHCI [=m])
-# -> SDHCI platform and OF driver helper (MMC_SDHCI_PLTFM [=m])
-#
-#
-#
-# CONFIG_MMC_SDHCI_OF_DWCMSHC is not set
--
2.27.0
3 years, 10 months
[OS-BUILD PATCH] Makefile.common: Do not pre-maturely bump version
number
during merge window
by GitLab Bridge on behalf of dzickusrh
From: Don Zickus <dzickus(a)redhat.com>
I am not sure why the version number is bumped for rc0, but it causes
the rpm to build with the wrong version number. This puts the kernel
modules in the wrong directory and the booted kernel can't find them.
For example, currently the 5.8-rc1 merge window has 5.7.0 in the top
level Makefile. But the kernel.spec puts the modules in 5.8.0-0.rc0
directory which doesn't match.
I believe this was for legacy reasons, but forgot why. Not sure why we
are suddently seeing this after a year. This might be the first time
we tried building a kernel before -rc1 is officially out.
Signed-off-by: Don Zickus <dzickus(a)redhat.com>
---
redhat/Makefile.common | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/redhat/Makefile.common b/redhat/Makefile.common
index d980847aacc7..ff5e0853fc40 100644
--- a/redhat/Makefile.common
+++ b/redhat/Makefile.common
@@ -53,15 +53,6 @@ endif
ifeq ($(SNAPSHOT),1)
# The base for generating tags is the snapshot commit
MARKER:=$(shell echo $(TAG) | cut -d "g" -f 2)
- # The merge window is weird because the actual versioning hasn't
- # been updated but we still need something that works for
- # packaging. Fix this by bumping the patch level and marking
- # this as rc0
- ifeq ($(RPMKEXTRAVERSION),)
- KEXTRAVERSION:=.rc0
- PREBUILD:=0$(KEXTRAVERSION).
- RPMKPATCHLEVEL:=$(shell expr $(RPMKPATCHLEVEL) + 1)
- endif
# Follow the packaging guidelines to include the date + git snapshot
PREBUILD:=$(PREBUILD)$(shell date +%Y%m%d)git$(MARKER).
UPSTREAM_TARBALL_NAME:=$(shell date +%Y%m%d)git$(MARKER)
--
2.27.0
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in lib/math
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_PRIME_NUMBERS:
This option provides a simple prime number generator for test
modules.
If unsure, say N.
Symbol: PRIME_NUMBERS [=n]
Type : tristate
Defined at lib/math/Kconfig:8
Prompt: Simple prime number generator for testing
Location:
-> Library routines
Selected by [n]:
- DRM_DEBUG_SELFTEST [=n] && HAS_IOMEM [=y] && DRM [=m] && DEBUG_KERNEL [=y]
- DRM_I915_SELFTEST [=n] && HAS_IOMEM [=y] && EXPERT [=n] && DRM_I915 [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PRIME_NUMBERS | 1 +
.../generic/CONFIG_PRIME_NUMBERS | 20 -------------------
2 files changed, 1 insertion(+), 20 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PRIME_NUMBERS
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PRIME_NUMBERS
diff --git a/redhat/configs/common/generic/CONFIG_PRIME_NUMBERS b/redhat/configs/common/generic/CONFIG_PRIME_NUMBERS
new file mode 100644
index 000000000000..86f0c393140b
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PRIME_NUMBERS
@@ -0,0 +1 @@
+# CONFIG_PRIME_NUMBERS is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PRIME_NUMBERS b/redhat/configs/pending-common/generic/CONFIG_PRIME_NUMBERS
deleted file mode 100644
index 2e6a79c98670..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PRIME_NUMBERS
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_PRIME_NUMBERS:
-#
-# This option provides a simple prime number generator for test
-# modules.
-#
-# If unsure, say N.
-#
-# Symbol: PRIME_NUMBERS [=n]
-# Type : tristate
-# Defined at lib/math/Kconfig:8
-# Prompt: Simple prime number generator for testing
-# Location:
-# -> Library routines
-# Selected by [n]:
-# - DRM_DEBUG_SELFTEST [=n] && HAS_IOMEM [=y] && DRM [=m] && DEBUG_KERNEL [=y]
-# - DRM_I915_SELFTEST [=n] && HAS_IOMEM [=y] && EXPERT [=n] && DRM_I915 [=m]
-#
-#
-#
-# CONFIG_PRIME_NUMBERS is not set
--
2.27.0
3 years, 10 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: e5eaebafc509 - [redhat] kernel-5.7.0-20200610git5b14671be58d.1
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
Source RPM: FAILED (see build-generic.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We tried to create the SRPM package but failed.
3 years, 10 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: c0cb8923d3ce - [redhat] kernel-5.8.0-0.rc0.20200609gitabfbb29297c2.1
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
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.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=bpftool --with=selftests --with=kabidw_base --without=debug --without=ipaclones --without=perf --without=tools
3 years, 10 months
Streamlining the ARK config process
by Jeremy Cline
Hey folks,
Seeing the merge window configs rolling in along with people starting to
open GitLab merge requests rather than exclusively emailing patches, I
have a suggestion to make everyone's lives a bit easier, especially with
the configurations:
Start making use of the "developer" role[0] in GitLab. I recommend
reading over the permissions to get an idea of what's allowed, but the
short of it is developers can't push to protected branches, so can't
accidentally (or maliciously) change any of the important branches in
the repository, but they *can* modify non-protected branches like the
config branches[1], apply labels, and so on.
Rather than having a script set the configs, then someone review them,
ask the maintainer to change it, then review it again, then have the
maintainer merge it, you can just check out the config branch for the
merge request, change it yourself, push it, and mark it ready (or get
more reviews) for merging. This cuts down on a lot of back and forth so
it'll save everyone time.
[0] https://gitlab.com/help/user/permissions
[1] https://gitlab.com/cki-project/kernel-ark/-/branches/all?utf8=%E2%9C%93&s...
- Jeremy
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in drivers/dma-buf
by GitLab Bridge on behalf of jeremycline
From: Jeremy Cline <jcline(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_DMABUF_HEAPS:
Choose this option to enable the DMA-BUF userland memory heaps.
This options creates per heap chardevs in /dev/dma_heap/ which
allows userspace to allocate dma-bufs that can be shared
between drivers.
Symbol: DMABUF_HEAPS [=n]
Type : bool
Defined at drivers/dma-buf/Kconfig:47
Prompt: DMA-BUF Userland Memory Heaps
Location:
-> Device Drivers
-> DMABUF options
Selects: DMA_SHARED_BUFFER [=y]
Enabled at the request of Lyude Paul.
---
Cc: Don Dutile <ddutile(a)redhat.com>
Cc: Don Zickus <dzickus(a)redhat.com>
Cc: Lyude Paul <lyude(a)redhat.com>
---
.../common/generic/CONFIG_DMABUF_HEAPS | 1 +
.../generic/CONFIG_DMABUF_HEAPS | 19 -------------------
2 files changed, 1 insertion(+), 19 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_DMABUF_HEAPS
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DMABUF_HEAPS
diff --git a/redhat/configs/common/generic/CONFIG_DMABUF_HEAPS b/redhat/configs/common/generic/CONFIG_DMABUF_HEAPS
new file mode 100644
index 000000000000..f4f69ff9b0ca
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DMABUF_HEAPS
@@ -0,0 +1 @@
+CONFIG_DMABUF_HEAPS=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_DMABUF_HEAPS b/redhat/configs/pending-common/generic/CONFIG_DMABUF_HEAPS
deleted file mode 100644
index 93f2ccccb66f..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DMABUF_HEAPS
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_DMABUF_HEAPS:
-#
-# Choose this option to enable the DMA-BUF userland memory heaps.
-# This options creates per heap chardevs in /dev/dma_heap/ which
-# allows userspace to allocate dma-bufs that can be shared
-# between drivers.
-#
-# Symbol: DMABUF_HEAPS [=n]
-# Type : bool
-# Defined at drivers/dma-buf/Kconfig:47
-# Prompt: DMA-BUF Userland Memory Heaps
-# Location:
-# -> Device Drivers
-# -> DMABUF options
-# Selects: DMA_SHARED_BUFFER [=y]
-#
-#
-#
-# CONFIG_DMABUF_HEAPS is not set
--
2.27.0
3 years, 10 months
✅ PASS: Test report for kernel 5.6.17-300.fc32 (fedora-32)
by CKI Project
Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.6.17-300.fc32
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=45546868
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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
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:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 2:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ Storage blktests
ppc64le:
Host 1:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ Storage blktests
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
s390x:
Host 1:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ Storage blktests
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
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Ethernet drivers sanity
🚧 ⚡⚡⚡ CIFS Connectathon
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
🚧 ⚡⚡⚡ kdump - sysrq-c
Host 3:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ Storage blktests
Host 4:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 5:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Test sources: https://github.com/CKI-project/tests-beaker
💚 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 ⏱.
3 years, 10 months