From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Sage: Random exit failures on amd64
Date: Thu, 13 May 2010 22:08:05 -0500 [thread overview]
Message-ID: <1273806492.22330.7@ledaig> (raw)
In-Reply-To: <E4EE4AAAD8B22F4C89BD10D73F1393DB09095F00@e14mdb-01.zdv.Uni-Mainz.DE> (from cschwan@students.uni-mainz.de on Thu May 13 15:42:56 2010)
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
On 05/13/10 - 15:42:56, Schwan, Christopher wrote:
> Hi,
>
> I just backported the fixes from sage-core-4.4.1 in src_prepare() to
> sage-core-4.3.5 and noticed now the same failures on amd64 as
> reported by Steven with sage-4.4 - so I have done something wrong in
> src_prepare(). I dont see the reason right now and will investigate
> on that later - maybe some of you see it.
>
> Christopher
>
> PS: Commited from PC with wrong time - dont be confused when looking
> at the history. I hope this doesnt break git
>
Christopher,
I backported to sage-core-4.3.5 here and I get none of the random exit
failures. I didn't run the entire test suite but enough of it where
random exit failures should appear. If I include the 4.3.5 networkx
patch I get the same first four failures I had previously with 4.3.5
and no random exit failures to that point. If I backport to 4.4.alpha0
then random exit failures do appear. I didn't backport everything, only
sage-core. I did a diff on the c_lib directory after unpacking
backports for 4.3.5 and 4.4.alpha0. The only differences appear in
c_lib/src/interrupt.c and are associated with message printouts when
there are errors. So I believe that libcsage.so and its headers are the
same for 4.4.alpha0 as for 4.3.5.
I just realized, and it's too late to try now, that I didn't check the
notebook.
Steve
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-14 3:12 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 [this message]
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
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=1273806492.22330.7@ledaig \
--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