Hi Alex, On: Tuesday, October 30, 2007 12:25 PM Alexander Klink wrote:
> On Mon, Oct 29, 2007 at 07:46:58PM +0300, Petr Grigoriev wrote: >> > On Monday, October 29, 2007 6:00 PM Alexander Klink wrote: >> >> Revision 1119 does not pass workflow tests ( see for example >> >> http://build0.cynops.de/openxpki_tests/server/1119_output.txt ). >> > I believe this is due to the fact that IPC::ShareLite was not yet >> > installed on build0. The tests pass just fine on my Mac OS X >> > development >> > box. >> 15_csr_and_certificate_issuance.t fails on FreeBSD with IPC::ShareLite >> installed. >> It says I18N_OPENXPKI_TRANSPORT_SIMPLE_CLIENT_READ_CLOSED_CONNECTION. >> Revision 1118 passes this test without any trouble. > Hmmm, weird, it passes both on my Mac OS X machine and build0 (the > failing workflow test is only because the CSR workflow is not yet in > SUCCESS, I'll implement a waiting similar to the one for the certificate > issuance workflow soon). Could you please debug that a bit further? > What does the stderr.log of the server say with DEBUG=1? Sorry for not answering for a long time but I had feeling that something was wrong in my system. Actually it was: FreeBSD port deve/p5-IPC-ShareLite needs some patching discussed 2 years ago here http://lists.freebsd.org/pipermail/freebsd-perl/2005-November/000772.html I do not know why it was not commited in time but after I have applied this patch and reinstall IPC::ShareLite 15_csr_and_certificate_issuance.t works OK. The problem concerns using malloc in FreeBSD and Perl. Tests for this package also fail without the patch - that is why I believe it is the main reason of my trouble. >> > The workflow looping test should be pretty obsolete after this change >> > anyhow, as we do not do looping anymore. >> > >> The looping test could be used to check whether the workflow forking and >> parent-children signaling >> works OK. > OK, but I believe it needs to be rewritten completely for that and > does not deserve the "looping" name any longer ... OK I'll try to do this. >> > Yes, any child may tell the parent that it failed at any time, which >> > will lead to the parent failing as well. On the other hand, the >> > child_finished_successfully activity is only available for the last >> > calling child - as no other child has notified failure, we assume >> > that they exited successfully. >> Thank you Alex, then I'll try to figure out why does LDAP fail. >> BTW could it be due to double describing <action >> name="notify_parent_success"... >> ( in workflow_activity_certificate_ldap_publishing.xml and in >> workflow_activity_certificate_issuance.xml ) ? > Hmmm, I don't believe so, if I remember correctly, the action names > are only global within a workflow (which I believe to be a bug in > Workflow.pm, IMHO they should be local to a state), not the complete > config ... LDAP test is to be rewritten too because it uses the server launched by itself while after adding /trunk/perl-modules/core/trunk/t/60_workflow/09_deploy_and_start_testserver.t it has to use the common server instead (or restart it in a different configuration). LDAP publishing in the installed OpenXPKI works OK after I reinstalled patched IPC::ShareLite. So I have to fix tests ;-) Best regards, Petr ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
