-
Notifications
You must be signed in to change notification settings - Fork 57
Open
Description
Problem: this failed on the el9 CI builder
2026-02-03T16:31:24.9918053Z expecting success:
2026-02-03T16:31:24.9918247Z $set_faketime Jun 5 15:45 2016 &&
2026-02-03T16:31:24.9918573Z id=$(echo "0 0 30 Dec * flux event pub t.cron.complete" | flux_cron tab) &&
2026-02-03T16:31:24.9918929Z next=$(date +%s --date="Dec 30 00:00") &&
2026-02-03T16:31:24.9919194Z cron_entry_check ${id} type datetime &&
2026-02-03T16:31:24.9919456Z cron_entry_check ${id} stopped false &&
2026-02-03T16:31:24.9919748Z cron_entry_check ${id} typedata.next_wakeup ${next} &&
2026-02-03T16:31:24.9920171Z ${event_trace} t.cron t.cron.complete \
2026-02-03T16:31:24.9920421Z $set_faketime Dec 30 00:00 &&
2026-02-03T16:31:24.9920667Z cron_entry_check ${id} stats.count 1 &&
2026-02-03T16:31:24.9920904Z flux cron delete ${id}
2026-02-03T16:31:24.9921041Z
2026-02-03T16:31:24.9921212Z timestamp file: @2016-06-05 15:45:00: date is now Sun Jun 5 15:45:00 UTC 2016
2026-02-03T16:31:24.9921561Z cron-5: type=datetime, wanted datetime
2026-02-03T16:31:24.9921811Z cron-5: stopped=false, wanted false
2026-02-03T16:31:24.9922094Z cron-5: typedata.next_wakeup=1483056000, wanted 1483056000
2026-02-03T16:31:24.9922474Z libfaketime: In parse_ft_string(), failed to parse FAKETIME timestamp.
2026-02-03T16:31:24.9922856Z Please check specification with format %Y-%m-%d %T
2026-02-03T16:31:24.9923144Z not ok 7 - flux-cron tab works for month
I was thinking this one had occasionally popped up for a long while, but didn't find an open issue.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels