Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=562504 --- Comment #10 from Thomas Spura <tomspur@xxxxxxxxxxxxxxxxx> 2010-02-08 14:02:40 EST --- (In reply to comment #8) > Furthermore the %check is ran in the build dir, so PYTHONPATH should be set to > PYTHONPATH=openmpi/ > for the Open MPI version etc. If ever, than it should be PYTHONPATH=openmpi/lib.linux-x86_64-2.6, so maybe PYTHONPATH=openmpi/lib.linux-* ? I don't like that '*' and would prefer running it, when installed. Or how do you like the '*' from above? (In reply to comment #9) > Doesn't work locally, either: > > + mpd --daemon > configuration file /builddir/.mpd.conf not found > A file named .mpd.conf file must be present in the user's home > directory (/etc/mpd.conf if root) with read and write access > only for the user, and must contain at least a line with: > MPD_SECRETWORD=<secretword> > One way to safely create this file is to do the following: > cd $HOME > touch .mpd.conf > chmod 600 .mpd.conf > and then use an editor to insert a line like > MPD_SECRETWORD=mr45-j9z > into the file. (Of course use some other secret word than mr45-j9z.) > error: Bad exit status from /var/tmp/rpm-tmp.L5Y4a4 (%check) > Bad exit status from /var/tmp/rpm-tmp.L5Y4a4 (%check) > RPM build errors: ok, I already have such a file here :( I don't want to add such a file on the buildsystem and without it won't work. How about disabling the mpich2 testsuite, till there is a 'sane' possibility? > You should run the mpd command right after %{_mpich2_load}. The MPICH2 package > is still blatantly in violation of the guidelines, which is why you can run > MPICH2 commands without loading the MPICH2 module. Done, works for me locally, but in koji fails becaus openmpi can't be initialized... + PYTHONPATH=/builddir/build/BUILDROOT/mpi4py-1.2-5.fc13.x86_64/usr/lib64/python2.6/site-packages/openmpi + python test/runalltest.py [x86-03.phx2.fedoraproject.org:18162] [[INVALID],INVALID] ORTE_ERROR_LOG: Not found in file ess_hnp_module.c at line 161 -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_plm_base_select failed --> Returned value Not found (-13) instead of ORTE_SUCCESS -------------------------------------------------------------------------- [x86-03.phx2.fedoraproject.org:18162] [[INVALID],INVALID] ORTE_ERROR_LOG: Not found in file runtime/orte_init.c at line 132 -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_ess_set_name failed --> Returned value Not found (-13) instead of ORTE_SUCCESS -------------------------------------------------------------------------- [x86-03.phx2.fedoraproject.org:18162] [[INVALID],INVALID] ORTE_ERROR_LOG: Not found in file orted/orted_main.c at line 323 [x86-03.phx2.fedoraproject.org:18161] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file ess_singleton_module.c at line 381 [x86-03.phx2.fedoraproject.org:18161] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file ess_singleton_module.c at line 143 [x86-03.phx2.fedoraproject.org:18161] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on the local node in file runtime/orte_init.c at line 132 RPM build errors: -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_ess_set_name failed --> Returned value Unable to start a daemon on the local node (-128) instead of ORTE_SUCCESS Don't know what to do here, except disabling the tests complete... Disabled for now: Spec URL: http://tomspur.fedorapeople.org/review/mpi4py.spec SRPM URL: http://tomspur.fedorapeople.org/review/mpi4py-1.2-5.fc12.src.rpm -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review