Sage: Ticket #9173: cygwin: BSD.py tests behave differently on cygwin, so need to be written to reflect that
https://trac.sagemath.org/ticket/9173
<pre class="wiki">
sage -t "devel/sage/sage/schemes/elliptic_curves/BSD.py"
**********************************************************************
File "/home/wstein/sage-4.4.3/devel/sage/sage/schemes/elliptic_curves/BSD.py", line 174:
sage: native_two_isogeny_descent_work(E, E.two_torsion_rank())
Expected:
(1, 1, 0, 0, None)
Got:
(0, 1, 0, 1, None)
**********************************************************************
File "/home/wstein/sage-4.4.3/devel/sage/sage/schemes/elliptic_curves/BSD.py", line 391:
sage: E.prove_BSD(verbosity=1, secs_hi=1)
Expected:
p = 2: True by 2-descent
Timeout stopped Heegner index computation...
Proceeding to use heegner_index_bound instead.
True for p not in {2, 3} by Kolyvagin.
[3]
Got:
p = 2: True by 2-descent
Timeout stopped Heegner index computation...
Proceeding to use heegner_index_bound instead.
True for p not in {2, 3, 5} by Kolyvagin.
True for p=5 by Stein-Wuthrich.
[3]
**********************************************************************
File "/home/wstein/sage-4.4.3/devel/sage/sage/schemes/elliptic_curves/BSD.py", line 426:
sage: E.prove_BSD(verbosity=1)
Expected:
p = 2: True by 2-descent
Timeout stopped Heegner index computation...
Proceeding to use heegner_index_bound instead.
True for p not in {2} by Kolyvagin.
[]
Got:
p = 2: True by 2-descent
Timeout stopped Heegner index computation...
Proceeding to use heegner_index_bound instead.
True for p not in {2, 3, 5} by Kolyvagin.
True for p=5 by Stein-Wuthrich.
p = 3 may divide the Heegner index, for which only a bound was computed.
ALERT: p = 3 left in Kolyvagin bound
0 <= ord_p(#Sha) <= 2
ord_p(#Sha_an) = 0
[3]
**********************************************************************
2 items had failures:
1 of 7 in __main__.example_4
2 of 34 in __main__.example_6
***Test Failed*** 3 failures.
</pre>en-usSagehttps://trac.sagemath.org/chrome/site/logo_sagemath_trac.png
https://trac.sagemath.org/ticket/9173
Trac 1.1.6drkirkbyTue, 08 Jun 2010 00:40:42 GMTcc set
https://trac.sagemath.org/ticket/9173#comment:1
https://trac.sagemath.org/ticket/9173#comment:1
<ul>
<li><strong>cc</strong>
<em>mhansen</em> added
</li>
</ul>
<p>
The same is happening on Solaris 10 on all the SPARC boxes I have access to - see <a class="closed ticket" href="https://trac.sagemath.org/ticket/9127" title="defect: BSD.py doctest failure due to timeout of Heegner index computation. (closed: fixed)">#9127</a> It appears to be a function of the speed of the computer, with timeouts occuring on slower hardware. I assume the overhead of Cygwin is causing this problem.
</p>
<p>
As such, I think this can probably be closed as a duplicate of <a class="closed ticket" href="https://trac.sagemath.org/ticket/9127" title="defect: BSD.py doctest failure due to timeout of Heegner index computation. (closed: fixed)">#9127</a>, which has positive review. You can try the patch there
</p>
<p>
<a class="ext-link" href="http://trac.sagemath.org/sage_trac/raw-attachment/ticket/9127/trac_9127.patch"><span class="icon"></span>http://trac.sagemath.org/sage_trac/raw-attachment/ticket/9127/trac_9127.patch</a>
</p>
<p>
Dave
</p>
TicketdrkirkbyTue, 08 Jun 2010 00:45:28 GMTcc changed
https://trac.sagemath.org/ticket/9173#comment:2
https://trac.sagemath.org/ticket/9173#comment:2
<ul>
<li><strong>cc</strong>
<em>cremona</em> added
</li>
</ul>
<p>
On closer inspection, it looks like the issues you are getting on Cygwin are larger than those on Solaris, as I have not seen the
</p>
<pre class="wiki">Expected:
(1, 1, 0, 0, None)
Got:
(0, 1, 0, 1, None)
</pre><p>
error - only the ones due to timeouts.
</p>
<p>
Dave
</p>
TicketkcrismanTue, 02 Aug 2011 02:26:28 GMT
https://trac.sagemath.org/ticket/9173#comment:3
https://trac.sagemath.org/ticket/9173#comment:3
<p>
This doctest passed on a build of mine on XP. In fact, the only files in schemes/ that failed were two in the plane conics section, probably because of "I" not working.
</p>
TicketkcrismanTue, 15 Jan 2013 15:49:28 GMTcc changed
https://trac.sagemath.org/ticket/9173#comment:4
https://trac.sagemath.org/ticket/9173#comment:4
<ul>
<li><strong>cc</strong>
<em>jpflori</em> added
</li>
</ul>
<p>
I get lots of forking errors now, because it "can't start pari".
</p>
TicketjpfloriTue, 15 Jan 2013 18:10:26 GMT
https://trac.sagemath.org/ticket/9173#comment:5
https://trac.sagemath.org/ticket/9173#comment:5
<p>
And the test passes for me (64bits W7 + 5.6.rc0).
</p>
TicketkcrismanTue, 15 Jan 2013 18:11:58 GMT
https://trac.sagemath.org/ticket/9173#comment:6
https://trac.sagemath.org/ticket/9173#comment:6
<blockquote class="citation">
<p>
And the test passes for me (64bits W7 + 5.6.rc0).
</p>
</blockquote>
<p>
Don't forget to try these by hand as well. In the past I've had failures only in the terminal.
</p>
TicketjpfloriTue, 15 Jan 2013 21:09:38 GMT
https://trac.sagemath.org/ticket/9173#comment:7
https://trac.sagemath.org/ticket/9173#comment:7
<p>
Replying to <a class="ticket" href="https://trac.sagemath.org/ticket/9173#comment:6" title="Comment 6">kcrisman</a>:
</p>
<blockquote class="citation">
<blockquote class="citation">
<p>
And the test passes for me (64bits W7 + 5.6.rc0).
</p>
</blockquote>
<p>
Don't forget to try these by hand as well. In the past I've had failures only in the terminal.
</p>
</blockquote>
<p>
You mean copy/paste the doctests in an interactive Sage session?
That's kind of boring isn't it? :)
</p>
TicketjpfloriTue, 15 Jan 2013 21:15:05 GMT
https://trac.sagemath.org/ticket/9173#comment:8
https://trac.sagemath.org/ticket/9173#comment:8
<p>
I tested some random examples and some from te failing ones quoting in the ticket description and had no problems.
</p>
TicketkcrismanWed, 16 Jan 2013 01:49:40 GMT
https://trac.sagemath.org/ticket/9173#comment:9
https://trac.sagemath.org/ticket/9173#comment:9
<blockquote class="citation">
<blockquote class="citation">
<blockquote class="citation">
<p>
And the test passes for me (64bits W7 + 5.6.rc0).
</p>
</blockquote>
<p>
Don't forget to try these by hand as well. In the past I've had failures only in the terminal.
</p>
</blockquote>
<p>
You mean copy/paste the doctests in an interactive Sage session?
That's kind of boring isn't it? :)
</p>
</blockquote>
<p>
Yes, you are right. But unfortunately I had some bad experiences with these Cygwin tests in the past so I figure I should ask - sorry :(
</p>
TicketjpfloriWed, 30 Jan 2013 10:48:00 GMTcc, status changed
https://trac.sagemath.org/ticket/9173#comment:10
https://trac.sagemath.org/ticket/9173#comment:10
<ul>
<li><strong>cc</strong>
<em>dimpase</em> <em>kcrisman</em> added; <em>mhansen</em> <em>cremona</em> removed
</li>
<li><strong>status</strong>
changed from <em>new</em> to <em>needs_review</em>
</li>
</ul>
TicketjpfloriFri, 08 Feb 2013 12:45:20 GMTstatus, milestone changed
https://trac.sagemath.org/ticket/9173#comment:11
https://trac.sagemath.org/ticket/9173#comment:11
<ul>
<li><strong>status</strong>
changed from <em>needs_review</em> to <em>positive_review</em>
</li>
<li><strong>milestone</strong>
changed from <em>sage-5.7</em> to <em>sage-duplicate/invalid/wontfix</em>
</li>
</ul>
<p>
No problems on another install, so let's close this one.
</p>
TicketjdemeyerFri, 08 Feb 2013 13:19:52 GMTstatus changed; reviewer, resolution set
https://trac.sagemath.org/ticket/9173#comment:12
https://trac.sagemath.org/ticket/9173#comment:12
<ul>
<li><strong>status</strong>
changed from <em>positive_review</em> to <em>closed</em>
</li>
<li><strong>reviewer</strong>
set to <em>Jean-Pierre Flori</em>
</li>
<li><strong>resolution</strong>
set to <em>worksforme</em>
</li>
</ul>
Ticket