| 1 |
On 05/13/10 - 15:42:56, Schwan, Christopher wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> I just backported the fixes from sage-core-4.4.1 in src_prepare() to |
| 5 |
> sage-core-4.3.5 and noticed now the same failures on amd64 as |
| 6 |
> reported by Steven with sage-4.4 - so I have done something wrong in |
| 7 |
> src_prepare(). I dont see the reason right now and will investigate |
| 8 |
> on that later - maybe some of you see it. |
| 9 |
> |
| 10 |
> Christopher |
| 11 |
> |
| 12 |
> PS: Commited from PC with wrong time - dont be confused when looking |
| 13 |
> at the history. I hope this doesnt break git |
| 14 |
> |
| 15 |
Christopher, |
| 16 |
|
| 17 |
I backported to sage-core-4.3.5 here and I get none of the random exit |
| 18 |
failures. I didn't run the entire test suite but enough of it where |
| 19 |
random exit failures should appear. If I include the 4.3.5 networkx |
| 20 |
patch I get the same first four failures I had previously with 4.3.5 |
| 21 |
and no random exit failures to that point. If I backport to 4.4.alpha0 |
| 22 |
then random exit failures do appear. I didn't backport everything, only |
| 23 |
sage-core. I did a diff on the c_lib directory after unpacking |
| 24 |
backports for 4.3.5 and 4.4.alpha0. The only differences appear in |
| 25 |
c_lib/src/interrupt.c and are associated with message printouts when |
| 26 |
there are errors. So I believe that libcsage.so and its headers are the |
| 27 |
same for 4.4.alpha0 as for 4.3.5. |
| 28 |
|
| 29 |
I just realized, and it's too late to try now, that I didn't check the |
| 30 |
notebook. |
| 31 |
|
| 32 |
Steve |
Archives