#4397: [with patch; need review] Sage 3.1.4: optional doctest failure in
sage/rings/number_field/number_field.py
----------------------+-----------------------------------------------------
 Reporter:  mabshoff  |        Owner:  was                           
     Type:  defect    |       Status:  closed                        
 Priority:  major     |    Milestone:  sage-duplicate/invalid/wontfix
Component:  doctest   |   Resolution:  invalid                       
 Keywords:            |  
----------------------+-----------------------------------------------------
Changes (by mabshoff):

  * status:  new => closed
  * resolution:  => invalid
  * milestone:  sage-3.2 => sage-duplicate/invalid/wontfix

Comment:

 I think the solution here are the two extcode patches that were missing
 from #2171. With those two patches applied and the database_gap.spkg
 installed I get
 {{{
 [EMAIL PROTECTED]:/scratch/mabshoff/release-cycle/sage-3.1.3.final$ ./sage -t
 -long -optional devel/sage/sage/rings/number_field/number_field.py
 sage -t -long -optional devel/sage/sage/rings/number_field/number_field.py
   ***   Warning: large Minkowski bound: certification will be VERY long.
   ***   Warning: large Minkowski bound: certification will be VERY long.

          [45.4 s]

 ----------------------------------------------------------------------
 All tests passed!
 Total time for all tests: 45.4 seconds
 }}}
 Hence: Invalid, sorry for the noise.

 Cheers,

 Michael

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4397#comment:3>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of 
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to