From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Sage: Random exit failures on amd64
Date: Sat, 15 May 2010 23:06:28 -0500 [thread overview]
Message-ID: <1273982797.30273.0@pavilion64> (raw)
In-Reply-To: <201005151437.53298.cschwan@students.uni-mainz.de> (from cschwan@students.uni-mainz.de on Sat May 15 07:37:53 2010)
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
On 05/15/10 07:37:53, Christopher Schwan wrote:
> Hi,
>
> On Saturday 15 May 2010 12:34:30 Christopher Schwan wrote:
>> [..]
>>
>> I am preparing a script which outputs a list of Sage's dependencies and
>> their versions so we can compare it.
>>
>> Christopher
>
> please checkout the recent overlay and run:
>
> ./list-compare-deps sage sage-clib sage-core sage-data sage-extcode sage-
> notebook sage-singular
>
> in the Tools subdirectory of our repository. This should list the
> dependencies
> of Sage compared with the version that are installed on your pc.
>
> Christopher
>
Christopher,
I hadn't masked things properly in backporting when using sage-core-4.3.5-r1
on my laptop. After fixing things and running the tests again I now have one
SIGABRT failure. I'm not sure if the fixes resulted in the failure or
something else triggered it. The only library change was ghmm. I've been
unable to get the test to fail when running it individually.
Steve
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-05-16 4:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 20:42 [gentoo-science] Sage: Random exit failures on amd64 Schwan, Christopher
2010-05-14 3:08 ` Steven Trogdon
2010-05-14 6:55 ` Christopher Schwan
2010-05-14 13:09 ` Steven Trogdon
2010-05-14 17:44 ` Steven Trogdon
2010-05-15 10:34 ` Christopher Schwan
2010-05-15 12:37 ` Christopher Schwan
2010-05-16 4:06 ` Steven Trogdon [this message]
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=1273982797.30273.0@pavilion64 \
--to=strogdon@d.umn.edu \
--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