Complete Yocto mirror with license table for TQMa6UL (2038-compliance)
- 264 license table entries with exact download URLs (224/264 resolved) - Complete sources/ directory with all BitBake recipes - Build configuration: tqma6ul-multi-mba6ulx, spaetzle (musl) - Full traceability for Softwarefreigabeantrag - GCC 13.4.0, Linux 6.6.102, U-Boot 2023.04, musl 1.2.4 - License distribution: GPL-2.0 (24), MIT (23), GPL-2.0+ (18), BSD-3 (16)
This commit is contained in:
@@ -0,0 +1,45 @@
|
||||
From 41103f017f6a233ebb477dd1712fe82ea8f1c84c Mon Sep 17 00:00:00 2001
|
||||
From: Tim Orling <tim.orling@konsulko.com>
|
||||
Date: Thu, 29 Feb 2024 08:45:54 -0800
|
||||
Subject: [PATCH] conftest.py: disable deadline
|
||||
|
||||
The deadline is by default 200ms, but this is intended to be useful to
|
||||
the developer and not necessarily recommended for heavily loaded CI
|
||||
systems. Avoid warnings by disabling the deadline completely.
|
||||
|
||||
https://github.com/HypothesisWorks/hypothesis/issues/3713
|
||||
https://hypothesis.readthedocs.io/en/latest/settings.html#hypothesis.settings.deadline
|
||||
https://lists.openembedded.org/g/openembedded-core/topic/104640034#196437
|
||||
|
||||
Fixes:
|
||||
"""
|
||||
Unreliable test timings! On an initial run, this test took 268.29ms,
|
||||
which exceeded the deadline of 200.00ms, but on a subsequent run it
|
||||
took 2.63 ms, which did not. If you expect this sort of variability in
|
||||
your test timings, consider turning deadlines off for this test by
|
||||
setting deadline=None.
|
||||
"""
|
||||
|
||||
Upstream-Status: Submitted [https://github.com/python-attrs/attrs/pull/1252]
|
||||
|
||||
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
|
||||
---
|
||||
conftest.py | 2 +-
|
||||
1 file changed, 1 insertion(+), 1 deletion(-)
|
||||
|
||||
diff --git a/conftest.py b/conftest.py
|
||||
index 144e5f3..fdead3d 100644
|
||||
--- a/conftest.py
|
||||
+++ b/conftest.py
|
||||
@@ -20,7 +20,7 @@ def _frozen(request):
|
||||
def pytest_configure(config):
|
||||
# HealthCheck.too_slow causes more trouble than good -- especially in CIs.
|
||||
settings.register_profile(
|
||||
- "patience", settings(suppress_health_check=[HealthCheck.too_slow])
|
||||
+ "patience", settings(suppress_health_check=[HealthCheck.too_slow], deadline=None)
|
||||
)
|
||||
settings.load_profile("patience")
|
||||
|
||||
--
|
||||
2.34.1
|
||||
|
||||
Reference in New Issue
Block a user