On Thu, Sep 25, 2008 at 4:10 PM, William Stein <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 25, 2008 at 3:40 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>>
>>
>>
>> On Sep 25, 2:39 pm, Nick Alexander <[EMAIL PROTECTED]> wrote:
>>> On 25-Sep-08, at 2:36 PM, John Cremona wrote:
>>>
>>>
>>>
>>>
>>>
>>> > 2008/9/25 William Stein <[EMAIL PROTECTED]>:
>>>
>>> >> On Wed, Sep 24, 2008 at 3:42 AM, mabshoff <[EMAIL PROTECTED]>
>>> >> wrote:
>>>
>>> >>> Hello folks,
>>>
>>> >>> this is alpha1, a couple hours later than I wanted, but than a bunch
>>> >>> of things got in the way during the day. Sources are in the usual
>>> >>> place at
>>>
>>> >>>http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.3/sa...
>>>
>>> >> I thought we slayed this, but on eno we have this weird failure:
>>>
>>> >> sage -t -long devel/sage/sage/rings/
>>> >> finite_field_ntl_gf2e
>>> >> .pyx
>>> >> **********************************************************************
>>> >> File "/home/wstein/eno/build/sage-3.1.3.alpha1/tmp/
>>> >> finite_field_ntl_gf2e.py",
>>> >> line 167:
>>> >> sage: k.modulus()
>>> >> Expected:
>>> >> x^1024 + x^19 + x^6 + x + 1
>>> >> Got:
>>> >> x^1024 + x^16 + x^15 + x^14 + x^13 + x^11 + x^10 + x^9 + x^7 +
>>> >> x^6 + x^2
>>> >> **********************************************************************
>>> >> 1 items had failures:
>>> >> 1 of 10 in __main__.example_2
>>> >> ***Test Failed*** 1 failures.
>>>
>>> > That is strange, since the constructor for degree up to 2048 uses a
>>> > precomputed table (in NTL) so should definitely not change.
>>>
>>> Also note that the result is reducible.
>>>
>>> Nick
>>
>> Yes, that is really the odd thing. IIRC last time we fixed this we
>> turned some weak references into references and the problem magically
>> went away. Unfortunately this bug seems to be a Zombie and I have no
>> clue how to debug this :(
>>
> It is definitely a heisenbug. I just tried the test on the same machine
> again
> 10 times and it passes every time:
>
> [EMAIL PROTECTED] sage-3.1.2]$ ./sage -t --long
> devel/sage/sage/rings/finite_field_ntl_gf2e.pyx
> sage -t --long devel/sage/sage/rings/finite_field_ntl_gf2e.pyx
> [1.2 s]
>
> ----------------------------------------------------------------------
> All tests passed!
> Total time for all tests: 1.2 seconds
WAIT! I was just testing 3.1.2, which is behind the times.
With 3.1.3.alpha1 it fails every time the same way (see below).
I then turned *off* caching again for finite fields and the problem
goes away. SO, somebody turned caching from off back to
on in a patch that goes from 3.1.2 to 3.1.3.alpha1. And turning
caching on not surprisingly breaks things.
[EMAIL PROTECTED] sage-3.1.3.alpha1]$ ./sage -t
devel/sage/sage/rings/finite_field_ntl_gf2e.pyx
sage -t devel/sage/sage/rings/finite_field_ntl_gf2e.pyx
**********************************************************************
File "/home/wstein/eno/build/sage-3.1.3.alpha1/tmp/finite_field_ntl_gf2e.py",
line 167:
sage: k.modulus()
Expected:
x^1024 + x^19 + x^6 + x + 1
Got:
x^1024 + x^16 + x^15 + x^14 + x^13 + x^11 + x^10 + x^9 + x^7 + x^6 + x^2
**********************************************************************
1 items had failures:
1 of 10 in __main__.example_2
***Test Failed*** 1 failures.
For whitespace errors, see the file
/home/wstein/eno/build/sage-3.1.3.alpha1/tmp/.doctest_finite_field_ntl_gf2e.py
[1.2 s]
exit code: 1024
----------------------------------------------------------------------
The following tests failed:
sage -t devel/sage/sage/rings/finite_field_ntl_gf2e.pyx
Total time for all tests: 1.2 seconds
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
