Hi Nathann,
On Fri, Jul 9, 2010 at 3:44 PM, Nathann Cohen wrote:
> only have one thing to do : you are talking about studying them -->
> can you point me to any such book/website ?
This document explains some common techniques for testing software:
www.chillarege.com/authwork/TestingBestPractic
Throttling is off.
Build error:
STAGE 2-1-2: CacheEdge DETECTION
make -f Makefile INSTALL_LOG/atlas_cacheedge.h pre=d 2>&1 | ./
xatlas_tee INSTALL_LOG/dMMCACHEEDGE.LOG
make[3]: *** [build] Ошибка 255
make[3]: Выход из каталога `/mnt/data/Distr/Sage/sage-4.4.4/spkg/build/
atlas-3.8.3.p12/ATLAS-buil
On 07/09/2010 12:46 AM, Pat LeSmithe wrote:
> I get many failures [1] when I run, e.g.,
>
> ./sage -tp 22 -long -sagenb -randorder=42 devel/sage
That should be '-randorder=12345' to match the results quoted below.
For full raw test logs, please see
http://trac.sagemath.org/sage_trac/ticket/9461
I get many failures [1] when I run, e.g.,
./sage -tp 22 -long -sagenb -randorder=42 devel/sage
with an otherwise long-doctest-passing Sage 4.5.alpha4 on sage.math.
I've opened
http://trac.sagemath.org/sage_trac/ticket/9461
[1] Nearly all seem to be reproducible. The following tests "failed:"
I have run the "sage" and click notebook()
Start firefox: http://localhost:8000
I had to wait a few minutes.
Soot is very slow.
The calculation was unable to run.
Timeouts connection with the server all the time.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscrib
> There does seem to be a few reports of ATLAS failures. See the ticket
>
> http://trac.sagemath.org/sage_trac/ticket/9385
>
> One (very very remote) possibility is that MAKEFLAGS was recently unset in
> ATLAS, though if anything I would expect that to make the build more stable,
> not
> less so.
Nice, though usually I already know about and don't have time to/don't
feel competent to review them ;)
I particularly like this function:
{{{
def people_to_bug(self):
}}}
- kcrisman
On Jul 8, 6:02 pm, William Stein wrote:
> Hi,
>
> I just spent a few hours and wrote a "Sage Nagbot". You
On Thu, Jul 8, 2010 at 3:52 PM, Alex Ghitza wrote:
>> Some of you will thus get emails.
>> I just wrote this, so it surely isn't perfect.
>
> I love it :)
Me too.
Another enhancement would be to analyze the patch(es) on the ticket to
see which files/lines are changed. Then, you can look at the
On 07/ 8/10 07:39 PM, William Stein wrote:
Hi,
Adding a new repository in SAGE_ROOT, and not getting rid of any
existing repositories is absolutely trivial to implement.
Yes.
Proposals about getting rid of existing repositories or merging them
are good to think about, but are potentially ver
On Fri, 9 Jul 2010 00:02:44 +0200, William Stein wrote:
> I just spent a few hours and wrote a "Sage Nagbot". You may have
> received an email from it.
> It analyzes each ticket on trac that "needs review", and if it can
> find somebody that it things is
> likely to be able to review the ticket,
Hi folks,
The following line seems to reset the sage interpreter (with n bigger
than 98), which is very annoying as it is a trivial matrix inversion
using numpy.
import numpy as np
n = 98
lhs = np.eye( n )
rhs = np.ones( n )
np.linalg.solve(lhs,rhs)
(then np is not defined anymore, nor n, lhs or
On Jul 8, 11:39 am, William Stein wrote:
> Hi,
>
> Adding a new repository in SAGE_ROOT, and not getting rid of any
> existing repositories is absolutely trivial to implement.
I don't know about trivial. What do you post on a trac ticket to
create a new hg repository?
Anyway, I've taken a shot:
Hi,
I just spent a few hours and wrote a "Sage Nagbot". You may have
received an email from it.
It analyzes each ticket on trac that "needs review", and if it can
find somebody that it things is
likely to be able to review the ticket, it sends an email to them.
Some of you will thus get emails.
I
On 07/ 8/10 09:06 PM, Ренат Ескенин wrote:
sage: An error occurred while installing atlas-3.8.3.p12
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of .../install.log. Describe your computer, operating system, etc.
erro
In my experience the files that needs more resources when building Sage are
the ones in the sage interfase for linbox
(i.e. src/interfaces/sage/linbox-sage.C)
It would be really nice if something can be done to speed up the
compilation of this file
and make it use less memory (so that sage can be b
Hello!
I've talked about making Sageable interface to ALGLIB two months ago.
It took twice as much time as I previously thought, but now it is
ready to go public.
You can download first beta of ALGLIB double precision interface (as
.spkg or .zip file) from
http://www.alglib.net/share/20
Hi,
There are 453 accounts on trac, and only 334 of those have their email
address set, though all should (optimally).
I noticed today that even *my* email wasn't set. Please visit
http://trac.sagemath.org/sage_trac/prefs
to confirm that your email address and full name are set correctly.
W
Hi Mike,
> > - Either handle such indentation
> > - Or at least emit a warning, at least upon x? and better during
> > the html documentation
> >
> > I guess this is an issue to be reported to sphinx, but I don't know
> > how to construct a self-contained plain sphinx call showing the is
Hi,
Adding a new repository in SAGE_ROOT, and not getting rid of any
existing repositories is absolutely trivial to implement.
Proposals about getting rid of existing repositories or merging them
are good to think about, but are potentially very, very difficult to
implement. Moreover, even if we
Hi,
On Thu, Jul 08, 2010 at 06:28:32PM +0200, Robert Miller wrote:
> > I sometimes wonder if it would be better if there was only one
> > repository for things except .spkg files. Perhaps rather than going
> > from 2 to 3 repositories, we should go from 2 to 1, and stick
> > everything in th
> I sometimes wonder if it would be better if there was only one
> repository for things except .spkg files. Perhaps rather than going
> from 2 to 3 repositories, we should go from 2 to 1, and stick
> everything in the new $SAGE_ROOT repository. (I suspect one can merge
> repositories, so informati
On 8 July 2010 16:54, John H Palmieri wrote:
> Right now, several important files are not under revision control:
> I propose that we place these under revision control. Specifically, I
> propose that we should put copies of these files in a directory local/
> bin (which is under revision cont
On Thu, Jul 8, 2010 at 5:54 PM, John H Palmieri wrote:
> Right now, several important files are not under revision control:
>
> - the plain text files in SAGE_ROOT: makefile, sage, README.txt,
> COPYING.txt, etc.
> - the plain text files in SAGE_ROOT/spkg: install, gen_html,
> README.txt, standard
Right now, several important files are not under revision control:
- the plain text files in SAGE_ROOT: makefile, sage, README.txt,
COPYING.txt, etc.
- the plain text files in SAGE_ROOT/spkg: install, gen_html,
README.txt, standard/deps, etc.
Recently, there has been a lot of work done on spkg/in
Hi!
On Jul 7, 5:38 pm, Simon King wrote:
> What I suggest would apply to all interfaces and to all classes
> deriving from Parent that use the generic implementation for that
> interface.
My suggestion is now a patch, namely for ticket #2420. It not only
provides the interface cache framework fo
25 matches
Mail list logo
