> FWIW,
>
> sage-4.0.1.alpha0 compiled without any hickups on my Blade 2000 running
> Solaris 10 update 6.
William Stein wrote:
> 2009/6/4 Dr. David Kirkby <david.kir...@onetel.net>:
>> FWIW,
>>
>> sage-4.0.1.alpha0 compiled without any hickups on my Blade 2000 running
>> Solaris 10 update 6.
>
> Did you run the test suite? I also built from scratch
> sage-4.0.1.alpha0 on a Blade 2000 (I think), and 5 file didn't pass
> the suite for me. 3 were due to timeouts (the machine was loaded),
> so I just need to retest those again, 1 was trivial numerical noise,
> which has been fixed in rc0, and 1 was a genuine bug in the bitset
> data structure. Robert Bradshaw is working on the bitset bug right
> now.
I've not run the tests on sage-4.0.1.alpha0. I'll do that. I did it on
sage-4.0.rc0 and posted the results. You appeared to be aware of them
all except one. I'll run them on sage-4.0.1.alpha0 too.
I don't know if you see my note about the difference between
sage-4.0.rc0 and sage-4.0.rc1 regarding the secure notebook.
sage-4.0.rc1 generates the traceback (like below) but sage-4.0.rc0 does
not, but hangs generating the keys - even when left overnight.
There appeared to be a change in
devel/sage-main/sage/server/notebook/run_notebook.py between
sage-4.0.rc0 and sage-4.0.rc1, as a 'diff' on the two versions shows
some changes.
Note also, that 'certtool' that is used to generate the keys is not
included in a standard install of Solaris 10. I happened to have it from
Blastwave, but it should not be assumed to be present in Solaris. That
command works fine from the unix command line for me, but not when
called from Sage.
> Regarding the notebook, we'll eventually get to the bottom of that. I
> don't know what the problem is. Have you got an account on
> t2.math.washington.edu yet? If so, it would be *extremely* useful if
> you could build Sage there (I haven't yet!), since then I could
> directly debug this notebook problem.
You offered me an account on t2.math.washington.edu and I replied by
email saying I'd like one and copying it to whoever you asked (forget
who now), but I don't have one yet. If you can sort that out, I'll build
Sage on there. A username of 'drkirkby' would be my choice. Just email
me a password and I'll change it when I log in.
A lof of Sun SPARCs in common use are not as fast as the modern
Intel/AMD machines. I had a few time-out failures myself on this Blade
2000. Perhaps the time-limits should be increased somewhat, or some
option to increase the timeouts by a factor of 5 if someone wanted to do
it on older machines.
This machine is heavily loaded and is 2 x 1200 MHz. There are a *lot* of
people running slower SPARC machines than this one. (In fact, I have a
couple here with 450 MHz processors, and another with a 500 MHz processor).
Dave
> William
>
>> Again, like any version of Sage I've tried (including the binary Micheal
>> compiled), the GUI interface, with
>>
>> 'notebook()'
>>
>> will not work for me. I'm unable to find any server listening on port
>> 80000.
>>
>> Attempting to use the secure server, generates a traceback which Sage
>> reports might be corrupt, despite the fact that $HOME/.sage was removed
>> first. See below.
>>
>>
>> drkir...@kestrel:[~/sage/sage-4.0.1.alpha0] $ rm -r $HOME/.sage
>> drkir...@kestrel:[~/sage/sage-4.0.1.alpha0] $ ./sage
>> ----------------------------------------------------------------------
>> | Sage Version 4.0.1.alpha0, Release Date: 2009-05-31 |
>> | Type notebook() for the GUI, and license() for information. |
>> ----------------------------------------------------------------------
>> Setting permissions of DOT_SAGE directory so only you can read and write it.
>> sage: notebook(secure=True)
>> The notebook files are stored in: /export/home/drkirkby/.sage//sage_notebook
>>
>>
>> Please choose a new password for the SAGE Notebook 'admin' user.
>> Do _not_ choose a stupid password, since anybody who could guess your
>> password
>> and connect to your machine could access or delete your files.
>> NOTE: Only the md5 hash of the password you type is stored by SAGE.
>> You can change your password by typing notebook(reset=True).
>>
>>
>>
>> Enter new password:
>> Retype new password:
>> Please login to the notebook with the username 'admin' and the above
>> password.
>> Password changed for user 'admin'.
>> In order to use an SECURE encrypted notebook, you must first run
>> notebook.setup().
>> Now running notebook.setup()
>> Using dsage certificates.
>> ERROR: An unexpected error occurred while tokenizing input
>> The following traceback may be corrupted or invalid
>> The error message is: ('EOF in multi-line statement', (5, 0))
>>
>> ---------------------------------------------------------------------------
>> NameError Traceback (most recent call last)
>>
>> /export/home/drkirkby/.sage/<ipython console> in <module>()
>>
>> /export/home/drkirkby/sage/sage-4.0.1.alpha0/local/lib/python2.5/site-packages/sage/server/notebook/notebook_object.pyc
>> in __call__(self, *args, **kwds)
>> 163 """
>> 164 def __call__(self, *args, **kwds):
>> --> 165 return self.notebook(*args, **kwds)
>> 166
>> 167 notebook = run_notebook.notebook_twisted
>>
>> /export/home/drkirkby/sage/sage-4.0.1.alpha0/local/lib/python2.5/site-packages/sage/server/notebook/run_notebook.pyc
>> in notebook_twisted(self, directory, port, address, port_tries, secure,
>> reset, accounts, require_login, server_pool, ulimit, timeout,
>> open_viewer, sagetex_path, start_path, fork, quiet)
>> 278 if open_viewer:
>> 279 "Open viewer automatically isn't fully implemented.
>> You have to manually open your web browser to the above URL."
>> --> 280 return run(port)
>> 281
>> 282
>>
>> /export/home/drkirkby/sage/sage-4.0.1.alpha0/local/lib/python2.5/site-packages/sage/server/notebook/run_notebook.pyc
>> in run(port)
>> 146 print "In order to use an SECURE encrypted
>> notebook, you must first run notebook.setup()."
>> 147 print "Now running notebook.setup()"
>> --> 148 notebook_setup()
>> 149 if not os.path.exists(private_pem) or not
>> os.path.exists(public_pem):
>> 150 print "Failed to setup notebook. Please try
>> notebook.setup() again manually."
>>
>> /export/home/drkirkby/sage/sage-4.0.1.alpha0/local/lib/python2.5/site-packages/sage/server/notebook/run_notebook.pyc
>> in notebook_setup(self)
>> 39 print "Using dsage certificates."
>> 40 dsage = os.path.join(DOT_SAGE, 'dsage')
>> ---> 41 sage.dsage.all.dsage.setup()
>> 42 shutil.copyfile(dsage + '/cacert.pem', private_pem)
>> 43 shutil.copyfile(dsage + '/pubcert.pem', public_pem)
>>
>> NameError: global name 'sage' is not defined
>> sage: version()
>> 'Sage Version 4.0.1.alpha0, Release Date: 2009-05-31'
>>
>>
>>
>>
>>
>>
>>
>
>
>
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
