#5807: dsage with @parallel doesn't work at all
--------------------+-------------------------------------------------------
Reporter: was | Owner: yi
Type: defect | Status: new
Priority: major | Milestone: sage-3.4.2
Component: dsage | Keywords:
--------------------+-------------------------------------------------------
Description changed by was:
Old description:
> I tried to use dsage with the @parallel directory and sage-3.4, and it's
> 100% broken. The log just spews forever:
> {{{
>
> 2009-04-16 18:25:05-0700 [-] [Worker: 0] Restarting...
> 2009-04-16 18:25:05-0700 [-] [Worker 0] Started...
> 2009-04-16 18:25:05-0700 [-] [Worker 1] Job vISI9r9Dzs failed!
> 2009-04-16 18:25:05-0700 [-] Traceback:
> execfile('/scratch/wstein/sage/dsage/tmp_worker_files/vISI9r9Dzs/f.py')
> re
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File
> "/scratch/wstein/sage/dsage/tmp_worker_files/vISI9r9Dzs/f.py", line 8, in
> <module>
> f = unpickle_function(p_f)
> NameError: name 'p_f' is not defined
>
> 2009-04-16 18:25:05-0700 [-] [Worker: 1] Restarting...
> 2009-04-16 18:25:05-0700 [-] [Worker 1] Started...
> 2009-04-16 18:25:05-0700 [Broker,client] [Worker 0] Starting job
> 5pzNNCImcd
> 2009-04-16 18:25:05-0700 [Broker,client] [Worker 1] Starting job
> vISI9r9Dzs
> }}}
>
> Using @parallel and multiprocessing for what I want to do (just some
> simple no-pexpect C library stuff involving modular symbols) doesn't work
> either, since I get weird pari_trap error exceptions.
>
> It is so sad, that after all these years and all this work to write code
> to run things in parallel, that even the most trivial basic thing that I
> would like to do in parallel, which is evaluate a function on a bunch of
> integer inputs, still doesn't work robustly.
New description:
I tried to use dsage with the @parallel directory and sage-3.4, and it's
100% broken. The log just spews forever:
{{{
2009-04-16 18:25:05-0700 [-] [Worker: 0] Restarting...
2009-04-16 18:25:05-0700 [-] [Worker 0] Started...
2009-04-16 18:25:05-0700 [-] [Worker 1] Job vISI9r9Dzs failed!
2009-04-16 18:25:05-0700 [-] Traceback:
execfile('/scratch/wstein/sage/dsage/tmp_worker_files/vISI9r9Dzs/f.py')
re
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File
"/scratch/wstein/sage/dsage/tmp_worker_files/vISI9r9Dzs/f.py", line 8, in
<module>
f = unpickle_function(p_f)
NameError: name 'p_f' is not defined
2009-04-16 18:25:05-0700 [-] [Worker: 1] Restarting...
2009-04-16 18:25:05-0700 [-] [Worker 1] Started...
2009-04-16 18:25:05-0700 [Broker,client] [Worker 0] Starting job
5pzNNCImcd
2009-04-16 18:25:05-0700 [Broker,client] [Worker 1] Starting job
vISI9r9Dzs
}}}
Using @parallel and multiprocessing for what I want to do (just some
simple no-pexpect C library stuff involving modular symbols) doesn't work
either, since I get weird pari_trap error exceptions:
{{{
Exception in thread Thread-6:
Traceback (most recent call last):
File "/home/wstein/sage/local/lib/python2.5/threading.py", line 486, in
__bootstrap_inner
self.run()
File "/home/wstein/sage/local/lib/python2.5/threading.py", line 446, in
run
self.__target(*self.__args, **self.__kwargs)
File "/home/wstein/sage/local/lib/python2.5/site-
packages/processing/pool.py", line 232, in _handleResults
for job, i, obj in iter(get, None):
File "/home/wstein/sage/local/lib/python2.5/site-
packages/sage/libs/pari/gen_py.py", line 59, in pari
return gen.pari(x)
File "gen.pyx", line 9125, in sage.libs.pari.gen._pari_trap
(sage/libs/pari/gen.c:39083)
PariError: (7)
}}}
It is so sad, that after all these years and all this work to write code
to run things in parallel, that even the most trivial basic thing that I
would like to do in parallel, which is evaluate a function on a bunch of
integer inputs, still doesn't work robustly.
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5807#comment:1>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
