Hi All,
The new tests added in revision 978 are designed to help fixing the bug
#1699848.
They work like this:
1) workflow I18N_OPENXPKI_WF_TYPE_CYCLE_TOP forks producing
workflow I18N_OPENXPKI_WF_TYPE_CYCLE_SUB
and waits for it checking if "wf_child_instance_finished" every second.
2) workflow I18N_OPENXPKI_WF_TYPE_CYCLE_SUB forks producing
workflow I18N_OPENXPKI_WF_TYPE_CYCLE_SUB2
and waits for it checking if "wf_child_instance_finished" every 3
seconds.
3) workflow I18N_OPENXPKI_WF_TYPE_CYCLE_SUB2 is doing nothing for 9 seconds
and goes in SUCCESS state.
4) then I18N_OPENXPKI_WF_TYPE_CYCLE_SUB goes in SUCCESS state and
I18N_OPENXPKI_WF_TYPE_CYCLE_TOP goes in SUCCESS state
At the moment the test in the case of fail dumps:
# $VAR1 = {
# 'LIST' => [
# {
# 'LABEL' =>
'I18N_OPENXPKI_SERVICE_DEFAULT_COMMAND_EXECUTION_ERROR',
# 'PARAMS' => {
# 'ERROR' => 'State
\'CHECK_CHILD_FINISHED\' should be automatically executed but there are
multiple actions available for execution. Actions are: null2, null'
# }
# }
# ],
# 'SERVICE_MSG' => 'ERROR'
# };
The reason according to logs is that two opposite conditions
( wf_child_instance_finished and !wf_child_instance_finished )
both appears to be valid. I cannot figure out why it happens.
It happens rather often.
It is better not to run the test in automated mode because
in the case of fail some processes can stay running in memory
(check it and clean it manually).
Best Regards,
Petr Grigoriev.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
OpenXPKI-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-devel
