Added a new optional parameter ignore_flaky_tests which is "false" by default (current behavior)
When set to "true" : flaky tests are considered as success and will generate a successful report
---------
Co-authored-by: Ghais Zaher <ghaiszaher@gmail.com>
if a job is aborted or suffers a critical failure, `always()` is not appropriate
> always
> Causes the step to always execute, and returns true, even when canceled. The always expression is best used at the step level or on tasks that you expect to run even when a job is canceled. For example, you can use always to send logs even when a job is canceled.
> Note: Avoid using always for any task that could suffer from a critical failure, for example: getting sources, otherwise the workflow may hang until it times out. If you want to run a job or step regardless of its success or failure, use the recommended alternative:if: success() || failure()
Source: https://docs.github.com/en/actions/learn-github-actions/expressions#always
Pierre-Hugues Laune
tinyboxvk
Ghais Zaher
Yeikel
Jan Waś
Juraj Misur
Casey
Renato Athaydes
Hyukjin Kwon