#15223: Let the `TestSuite` test that the construction of a parent returns the
parent
-------------------------------------+-------------------------------------
       Reporter:  SimonKing          |        Owner:
           Type:  defect             |       Status:  needs_work
       Priority:  major              |    Milestone:  sage-6.1
      Component:  coercion           |   Resolution:
       Keywords:  construction       |    Merged in:
  functor, test suite, sd53          |    Reviewers:
        Authors:  Simon King         |  Work issues:
Report Upstream:  N/A                |       Commit:
         Branch:                     |  cb4929aa68113ebdfe4e471a014f4621e42cdba7
  u/SimonKing/ticket/15223           |     Stopgaps:
   Dependencies:  #15229             |
-------------------------------------+-------------------------------------

Comment (by SimonKing):

 Replying to [comment:32 mmezzarobba]:
 > The failures do not look deterministic. With the current state of your
 branch, all tests passed when I did `sage -t integer_mod_ring.py` for the
 first time. Then I tried again and repeatedly got:
 > {{{
 > $ sage -t src/sage/rings/finite_rings/integer_mod_ring.py
 > Running doctests with ID 2013-12-28-16-42-51-6b28af73.
 > Doctesting 1 file.
 > sage -t src/sage/rings/finite_rings/integer_mod_ring.py
 > **********************************************************************
 > File "src/sage/rings/finite_rings/integer_mod_ring.py", line 729, in
 
sage.rings.finite_rings.integer_mod_ring.IntegerModRing_generic._pseudo_fraction_field
 > Failed example:
 >     Integers(15).fraction_field()
 > Expected:
 >     Traceback (most recent call last):
 >     ...
 >     TypeError: self must be an integral domain.
 > Got:
 >     Ring of integers modulo 15
 > }}}

 Ahahahaha! It looks like the same example (modulus 15) was used in a
 different example to demonstrate that one can erroneously claim that
 `IntegerModRing(15)` is a field, and it could be that by random order of
 executing the tests this false information was cached. To be on the safe
 side, we could empty the cache.

 > I will run the tests again after rebuilding sage from scratch.

 Did you pull from #15229?

 For the record: I get
 {{{
 sage -t src/sage/rings/residue_field.pyx  # 2 doctests failed
 sage -t src/sage/rings/polynomial/pbori.pyx  # 1 doctest failed
 sage -t src/sage/rings/finite_rings/finite_field_pari_ffelt.py  # 1
 doctest failed
 }}}

--
Ticket URL: <http://trac.sagemath.org/ticket/15223#comment:36>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to