Added by SLindoMansilla almost 6 years ago. Updated about 4 years ago.
0%
I don't think it would make sense to let jobs die on skip_post_fail_hook as then someone most likely would want the exact opposite. Instead I will document the implications.
okurz wrote:
I don't think it would make sense to let jobs die on skip_post_fail_hook as then someone most likely would want the exact opposite. Instead I will document the implications.
If someone wants their module to not fail using _SKIP_POST_FAIL_HOOKS, then os-autoinst already has "fatal" feature.
This is issue is still not resolved for me. I can reopen this ticket or create a new one. [functional][u], so I am not requesting that you do it.
SLindoMansilla wrote:
If someone wants their module to not fail using _SKIP_POST_FAIL_HOOKS, then os-autoinst already has "fatal" feature.
I don't understand what you mean by that. Can you clarify?
okurz wrote:
I don't understand what you mean by that. Can you clarify?
By default a module that fails will not abort the execution of following modules. When a module failure should abort the execution of following modules, then
sub test_flags {
return {fatal => 1};
}
is used.
This behavior is not respected when using _SKIP_POST_FAIL_HOOKS. So, it is not deciding if some would want to abort or not, it is about giving the openQA test developer the freedom to choose if the module should abort the job or not.
@asmorodskyi, as discussed with you, as you are working on it, assigning to you
asmorodskyi wrote:
Pull request is merged and deployed on osd