Actions
Bug #7522
closedschedule_simple fails
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
---------------------------------------------------------------------- ./30_generic_methods/schedule_simple.cf ---------------------------------------------------------------------- R: [ERROR] Promise could not be repaired, error encountered: Scheduling test1 R: TEST result ERROR test1: error test1_error false R: TEST result OK test1 R: [ERROR] Promise could not be repaired, error encountered: Scheduling test2 R: TEST result ERROR test2: error test2_error false R: TEST result OK test2 R: [ERROR] Promise could not be repaired, error encountered: Scheduling test3 R: TEST result ERROR test3: error test3_error false R: TEST result OK test3 R: TEST result ERROR test4: current_run 9 != 0 R: TEST result ERROR test4: run ${schedule_generic.run_id} != 1 R: TEST result ERROR test5: current_run 9 != 1 R: TEST result ERROR test6: current_run 349 != 1 R: /usr/rudder-tests/ncf/tests/acceptance/./30_generic_methods/schedule_simple.cf FAIL Return code is 0. ==> FAIL
This is at least related to the use of the date command:
# date --date='01/01/01 00:01' +%s date: illegal option -- - Usage: date [-n][-u] [mmddHHMM[[cc]yy]] [+Field Descriptors] Usage: date [-n][-u] [mmddHHMM[.SS[cc]yy]] [+Field Descriptors] Usage: date [-a] [[+|-]sss.fff]
Actions