Note : the answer now given by sage is another (valid) solution, as 
acceptable as the one expected, to the problem. This doctests the 
longest.path() method of (possibly directed) graphs. The doc hints at the 
use of LP methods to solve it. Since these LP methods often use random 
generation, not getting the same answer when two distincts solutions exists 
is not necessarily a problem, ab least in my eyes.

So this might be a glitch, even if it's not a fluke.

Hence another question : shouldn't the doctests either avoid multiple 
solutions problem if multiple solutions exist, or  test against the whole 
solution (set of all acceptable solution, if it can be finitely expressed) ?

HTH,

--
Emmanuel Charpentier

Le jeudi 27 novembre 2014 19:18:23 UTC+1, Emmanuel Charpentier a écrit :
>
> Compiles okay (I have to "make doc-clean ; make", though.
> Make ptestlong gives one error :
>
> **********************************************************************
> File "src/sage/graphs/generic_graph.py", line 6012, in 
> sage.graphs.generic_graph
> .GenericGraph.longest_path
> Failed example:
>     G.longest_path().edges()
> Expected:
>     [(0, 3, None), (2, 0, None)]
> Got:
>     [(0, 1, None), (2, 0, None)]
> **********************************************************************
>
> That's a first for me... Retrying it standalone gives the same result (i. 
> e. it's not a fluke).
>
> HTH,
>
> --
> Emmanuel Charpentier
>
> Le dimanche 23 novembre 2014 20:59:04 UTC+1, Volker Braun a écrit :
>>
>> Get the new "develop" git branch or source tarball: 
>> http://sage.sagedev.org/home/release/sage-6.5.beta1.tar.gz
>>
>> Mini-changelog:
>>
>> f16112c Updated Sage version to 6.5.beta1
>> 959d878 Merge hotfix 6.4.1 back into develop
>> 109a50c Trac #15534: Corrupt pickle in cluster_seed.py
>> ecab369 Trac #17375: Maxima should not need a working C compiler to run
>> e6d05f7 Trac #17296: Update autotools to 20141105
>> 1935dfa Trac #17354: change name of interval_iterator for posets
>> b265ec8 Trac #17349: R fails with version `GOMP_4.0' not found
>> dbe3ae2 Trac #17228: Implement CachedMethodCaller.precompute
>> 8a4535d Trac #16882: Upgrade to NTL 6.2.1
>> b36b323 Trac #17184: Upgrade to Singular-3-1-7p1
>> 7be83f0 Trac #17265: Add info on making tutorials from worksheets
>> 1a6585a Trac #11912: Clarify simplify_radical and Maxima's radcan
>> b5a5256 Trac #17343: _find_stale_files does not take OS into account
>> b9611ed Trac #16331: Game Theory: Build capacity to solve matching games 
>> in to Sage.
>> 1e9e8ba Trac #17369: sphinx-build is broken
>> 85026dd Trac #17366: for multivariate polynomial rings, degree method 
>> should convert its argument
>> 70abd68 Trac #12703: Update GLPK to 4.55
>> 7db0e02 Trac #17316: RegularMatroid.is_isomorphic returns false positives
>> 10fc4b3 Trac #16529: In python 3.x, reload() is renamed to imp.reload()
>> a38c35d Trac #17353: Smaller source tarballs
>> 1fc9ab6 Trac #17320: Memory leaks with LP Solvers are back
>> b5f0535 Trac #17028: Implement conversion vector -> PARI
>> 0250556 Trac #16570: Animate example looks broken
>> 7f124cb Trac #17356: Deprecation error in poset join_matrix
>> 603f9e0 Trac #17328: incomplete gamma function bugs for certain arguments
>> 58d1674 Trac #17318: openssl-dependent tests in notebook_ipython should 
>> be marked optional
>> 2833913 Trac #17267: Clean up mpfr, mpfi, mpc declarations
>> 3846ebf Trac #9671: Improve bar chart and histogram support
>> 00610dc Trac #17348: gcc 4.9.2 does not build on ARM
>> cc302b7 Trac #17125: More Sym and NSym functionality
>> f043df6 Trac #16640: Graphics3d.show abuses graphics_filename
>> 4d0a478 Trac #14506: Echelonize leads to wrong multiplication
>> 58d805f Trac #17352: Poset Documentation fix
>> 0463339 Trac #5956: image dimensions for show() are in inches
>> 0f25d41 Trac #17346: The sage-bdist script is not executable
>> 7a6d6c6 Trac #12847: Catalan: introduction to Sage
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Reply via email to