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.ChristopherPS: 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
pgpbdVRZAj8FO.pgp
Description: PGP signature
