Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dsage with @parallel doesn't work at all #5807

Closed
williamstein opened this issue Apr 17, 2009 · 3 comments
Closed

dsage with @parallel doesn't work at all #5807

williamstein opened this issue Apr 17, 2009 · 3 comments

Comments

@williamstein
Copy link
Contributor

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.

Component: dsage

Issue created by migration from https://trac.sagemath.org/ticket/5807

@williamstein

This comment has been minimized.

@williamstein
Copy link
Contributor Author

comment:2

Note that dsage is so broken that it isn't even possible to test this out. See #7975.

@williamstein
Copy link
Contributor Author

comment:3

Dsage is now deprecated.

@sagetrac-mvngu sagetrac-mvngu mannequin removed this from the sage-4.3.1 milestone Jan 19, 2010
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant