Ticket #7112 (closed defect: fixed)
[with patch; positive review] os x 10.5 powerpc -- there are many many doctest failures all over
| Reported by: | was | Owned by: | tbd |
|---|---|---|---|
| Priority: | blocker | Milestone: | sage-4.1.2 |
| Component: | doctest coverage | Keywords: | |
| Cc: | Work issues: | ||
| Report Upstream: | Reviewers: | ||
| Authors: | Merged in: | ||
| Dependencies: | Stopgaps: |
Description
----------------------------------------------------------------------
The following tests failed:
sage -t -long "devel/sage/sage/calculus/calculus.py"
sage -t -long "devel/sage/sage/misc/latex.py"
sage -t -long "devel/sage/sage/rings/number_field/totallyreal_rel.py"
sage -t -long "devel/sage/sage/schemes/elliptic_curves/ell_rational_field.py"
sage -t -long "devel/sage/sage/server/notebook/notebook.py"
sage -t -long "devel/sage/sage/server/simple/twist.py"
sage -t -long "devel/sage/sage/symbolic/expression.pyx"
Total time for all tests: 23343.5 seconds
pdlc424:~ wstein$
The complete testlog is here:
http://sage.math.washington.edu/home/wstein/patches/testlong-os10.5-ppc.log
Attachments
Change History
Changed 4 years ago by was
-
attachment
trac_7112.patch
added
comment:1 Changed 4 years ago by was
- Summary changed from os x 10.5 powerpc -- there are many many doctest failures all over to [with patch; needs review] os x 10.5 powerpc -- there are many many doctest failures all over
comment:2 Changed 4 years ago by was
I attached a patch trac_7112.patch that fixes all doctest issues:
- I couldn't reproduce the weird maxima-related solve doctest failure in the original log.
- I changed sage: print get_url('http://localhost:%s/simple/compute?session=%s&code=2*2' % (port, session)) to use a larger timeout, since on OS X 10.5 PPC the default timeout isn't enough for Sage to even startup.
- There is a numerical noise in ell_rational_field.py
- The output of totallyreal_rel.py was not deterministic so I sorted it.
- This dict_function({x/2: y^2, "hallo": "world"}) test latex.py is *impossible* to do right with more than one dictionary entry, since dictionaries are by definition in a random platform dependent order. So I made it a dictionary of length 1.
- The html output for the notebook.py test is a bit different on OS X. It doesn't matter so much since that code is deprecated in sage-4.1.2.
Changed 4 years ago by was
-
attachment
trac_7112-part2.patch
added
needed so that all tests also pass on sage.math.
comment:3 Changed 4 years ago by was
(Note that I already merged this in sage-4.1.2.rc1.alpha3. However, it awaits review before I'll release sage-4.1.2.)
comment:4 Changed 4 years ago by was
- Status changed from new to needs_review
- Summary changed from [with patch; needs review] os x 10.5 powerpc -- there are many many doctest failures all over to os x 10.5 powerpc -- there are many many doctest failures all over
comment:5 Changed 4 years ago by was
- Summary changed from os x 10.5 powerpc -- there are many many doctest failures all over to [with patch; needs review] os x 10.5 powerpc -- there are many many doctest failures all over
Old habits die hard...
comment:6 Changed 4 years ago by kcrisman
For reference for # 6642: the numerical noise issue in calculus.py was also noticed on #6642.
comment:7 Changed 4 years ago by kcrisman
- Status changed from needs_review to needs_work
- Summary changed from [with patch; needs review] os x 10.5 powerpc -- there are many many doctest failures all over to [with patch; needs work] os x 10.5 powerpc -- there are many many doctest failures all over
I hate to tell you this...
For some reason on PPC X.4, I actually got a different answer, forget the sorting, on the item in part2. I don't know why, but '5' did not show up in the list. Indeed, it must not have Same running the commands separately. Even more aggravating, doctests pass now BUT if I do it "by hand", I still don't get 5, no matter what I do. And it looks like that must be the case on your X.5 PPC as well, since you removed the five in the first patch.
But on Macintel X.5, I get the 5, as I also do on sagenb.org. So I assume that the '5' is right, BUT the answer is definitely different on PPC. What now? Is there a way to mark this test as being dependent? Or should there be a ... in the test? Or is there a bug in the code for integral_elements_in_box?
On the plus side, everything else is great!
comment:8 Changed 4 years ago by GeorgSWeber
- Status changed from needs_work to needs_review
- Summary changed from [with patch; needs work] os x 10.5 powerpc -- there are many many doctest failures all over to [with patch; needs review] os x 10.5 powerpc -- there are many many doctest failures all over
From just reading the patch(es), this is a positive review. The
sage -t -long devel/sage/sage/rings/number_field/totallyreal_rel.py
will still fail however, there is a deeper problem lurking in that one point of a certain lattice sitting in a certain rectangle is missed in the computations on a PPC platform --- but that would be another ticket. Let the doctest fail for the time being, the enhancements by the patch(es) for this ticket here are needed anyway, I guess.
All I need is to really test the whole patch(es) on my PPC, but #7186 was holding me up (the very first file, calculus.py, did show a very nasty doctest output ...), so I have to postpone this for yet another day (i.e. night, sigh ...).
comment:10 Changed 4 years ago by GeorgSWeber
- Summary changed from [with patch; needs review] os x 10.5 powerpc -- there are many many doctest failures all over to [with patch; positive review] os x 10.5 powerpc -- there are many many doctest failures all over
Do I need to change both the title and press the button? Hmm, I'll check the Wiki.
comment:11 Changed 4 years ago by was
- Status changed from positive_review to closed
- Resolution set to fixed

with this patch applied all doctest pass for me on OS X 10.5 PPC