- This covers failures propagated to evaluateScheduleTrigger() in AbstractScheduler class related to ScheduleTrigger such as (Invalid Expressions, Inputs resolving Issues...)
If a test mis-behave, for ex starting an execution but not terminating it, as the default termination grace period is 5mn it can take very long time to wait for post-test terminaison.
Switching to a termination grace period of 5s may help.
I also detect that the ExecutionControllerRunner test when launching the test suite, would not properly kill the `sleep-long` flow so waiting for it to complete, or the termination grace period. When a test that use this flow is launched separatly it works properly. As a safety net I reduce the sleep from 5mn to 30s.
* feat(tests): add annotation and modify CI to handle flaky tests, play them but not fail
* feat(tests): add description to flaky annotation
* fix(tests): add flaky to to KV sanity check
* fix(tests): typo
* feat(tests): add a flaky test
---------
Co-authored-by: nKwiatkowski <nkwiatkowski@kestra.io>
- Logs errors from the Executor catched execution
- Logs errors from the Scheduler catched execution
- Avoid most places where the warning "unable to change state already..." could occur
- Log using the run context logger flow issues from executable tasks so they appears inside execution logs
* test: make AbstractExecutionRepositoryTest parallelizable
* feat(tests): play jdbc h2 tests in parallel
* fix(tests): failing unit tests
* tests: add await until timeout on some tests
* fix(tests): failing unit tests
* fix(tests): failing unit tests
---------
Co-authored-by: nKwiatkowski <nkwiatkowski@kestra.io>
Co-authored-by: Nicolas K. <nk_mikmak@hotmail.com>
