[PATCH] gnu: python-crontab: Fix failing tests

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • TakeV
Owner
unassigned
Submitted by
TakeV
Severity
normal

Debbugs page

T
(address . guix-patches@gnu.org)(name . TakeV)(address . takev@disroot.org)
c749b128d996376778603ce54bf45b28c45de3ba.1731272083.git.takev@disroot.org
* gnu/packages/python-xyz.scm (python-crontab) [arguments]: Turn off frequency
at month check

Change-Id: Ia6a8f703119dc61ddc6b359fca161dfb5a21319d
---

Apparently this check fails on leap years.

gnu/packages/python-xyz.scm | 3 +++
1 file changed, 3 insertions(+)

Toggle diff (20 lines)
diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm
index 5083473c08..2d84bfa57e 100644
--- a/gnu/packages/python-xyz.scm
+++ b/gnu/packages/python-xyz.scm
@@ -29547,6 +29547,9 @@ (define-public python-crontab
"tests/test_frequency.py")
(("test_07_non_posix_shell")
"__off_test_07_non_posix_shell")
+ ;; Fails on leap years
+ (("test_19_frequency_at_month")
+ "__off_test_19_frequency_at_month")
;; AssertionError: 48 != 24
(("test_20_frequency_at_year")
"__off_test_20_frequency_at_year")))))))

base-commit: ee3219996b688d2c3336a7ea1e262308cf2d00b7
prerequisite-patch-id: 8e79e3033f6e8ae459eab31d7cf5149a8eb01e9c
prerequisite-patch-id: 2442dd8fbe7af78372dbf03871fb6c5506eb75fe
--
2.46.0
L
L
Ludovic Courtès wrote 7 days ago
(name . TakeV)(address . takev@disroot.org)
87r07doozr.fsf@gnu.org
TakeV <takev@disroot.org> skribis:

Toggle quote (5 lines)
> * gnu/packages/python-xyz.scm (python-crontab) [arguments]: Turn off frequency
> at month check
>
> Change-Id: Ia6a8f703119dc61ddc6b359fca161dfb5a21319d

Applied, thanks!

Toggle quote (4 lines)
> + ;; Fails on leap years
> + (("test_19_frequency_at_month")
> + "__off_test_19_frequency_at_month")

An interesting time trap…

Ludo’.
Closed
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 74302@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 74302
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch