From: "François Bissey" <f.r.bissey@massey.ac.nz>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] notebook backtrace
Date: Fri, 30 Apr 2010 13:54:32 +1200 [thread overview]
Message-ID: <201004301354.32332.f.r.bissey@massey.ac.nz> (raw)
In-Reply-To: <1272589176.26964.0@ledaig>
> sage -t -force_lib "devel/sage/doc/en/tutorial/tour_advanced.rst"
That particular one works for me. I am running the full test suite at
the moment. I will probably run the tests on ppc over the week end
as well, that may be interesting.
The only thing that jump at my mind for that test would be
scipy. You should have 0.7.1 not 0.7.2 as there has been a change
of interface, that would do that kind of things I think.
But that's a shot in the dark and that wouldn't solve the first
problem you reported.
Francois
next prev parent reply other threads:[~2010-04-30 1:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 15:27 [gentoo-science] notebook backtrace Steven Trogdon
2010-04-30 0:18 ` François Bissey
2010-04-30 0:59 ` Steven Trogdon
2010-04-30 1:09 ` François Bissey
2010-04-30 1:13 ` Steven Trogdon
2010-04-30 1:54 ` François Bissey [this message]
2010-04-30 21:52 ` Steven Trogdon
2010-04-30 22:15 ` François Bissey
2010-04-30 22:30 ` Steven Trogdon
2010-04-30 22:47 ` François Bissey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201004301354.32332.f.r.bissey@massey.ac.nz \
--to=f.r.bissey@massey.ac.nz \
--cc=gentoo-science@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox