On Jan 31, 1:20 pm, "Georg S. Weber" <georgswe...@googlemail.com>
wrote:
<SNIP>
> P.S.:
> There is another issue revealed by this build failure reported above.
> I always run on the command line "MAKE && MAKE testlong" so after some
> hours/overnight/etc. the end result is there without further
> interaction of mine.
>
> Now the second "MAKE testlong" also tried to continue with the build,
> of course failed building cddlib --- but then the doctesting started
> nevertheless?!
Yes, that is a known issue that I have hit before.
> IMHO this is not OK, doctesting does not make sense if the build
> itself errors out.
> (Poke me if you need the log, but they don't seem to contain
> enlightening details about that --- and this behaviour should be
> easily reproducible.)
>
> Same questionagain: Do we open a trac ticket?
Sure, I never opened a ticket for that one. Some script does not
properly return a non-zero status to make and then the testing blows
up. It even happens with a simple "make testlong"
if the build phase breaks.
> Cheers,
> gsw
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
