On 11/24/2010 03:52 PM, David Kirkby wrote: > On 24 November 2010 20:07, William Stein <wst...@gmail.com> wrote: >> On Wed, Nov 24, 2010 at 10:22 AM, David Kirkby <david.kir...@onetel.net> >> wrote: >>> I copied a complete file system containing my home directory (and so a >>> build of Sage) from one machine to another. I then run all the doc >>> tests. One test failed on the new machine, despite all tests passing >>> on the original machine. >>> >>> The following tests failed: >>> >>> sage -t -force_lib "devel/sage/sage/misc/preparser.py" >>> Total time for all tests: 10776.5 seconds >>> >>> When I look at the test failure, it appears that the test tried to >>> compile a file, which would not work, as the system had no gcc or >>> other compiler. >>> >>> drkir...@laptop:~/sage-4.6.1.alpha2$ ./sage -t -force_lib >>> "devel/sage/sage/misc/preparser.py" >>> sage -t -force_lib "devel/sage/sage/misc/preparser.py" >>> ********************************************************************** >>> File >>> "/export/home/drkirkby/sage-4.6.1.alpha2/devel/sage/sage/misc/preparser.py", >>> line 1484: >>> sage: z=0; sage.misc.preparser.load(t,globals()) >>> Expected: >>> Compiling ....pyx... >>> hi 0 >>> Got: >>> Compiling /export/home/drkirkby/.sage//temp/laptop/21516//tmp_2.pyx... >>> Error compiling cython file: >>> Error compiling >>> /export/home/drkirkby/.sage//temp/laptop/21516//tmp_2.pyx: >>> running build >>> running build_ext >>> building '_export_home_drkirkby__sage_temp_laptop_21516_tmp_2_pyx_0' >>> extension >>> creating build >>> creating build/temp.solaris-2.11-i86pc-2.6 >>> gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall >>> -Wstrict-prototypes -fPIC >>> -I/export/home/drkirkby/sage-4.6.1.alpha2/local/include/csage/ >>> -I/export/home/drkirkby/sage-4.6.1.alpha2/local/include/ >>> -I/export/home/drkirkby/sage-4.6.1.alpha2/local/include/python2.6/ >>> -I/export/home/drkirkby/sage-4.6.1.alpha2/local/lib/python2.6/site-packages/numpy/core/include >>> -I/export/home/drkirkby/sage-4.6.1.alpha2/devel/sage/sage/ext/ >>> -I/export/home/drkirkby/sage-4.6.1.alpha2/devel/sage/ >>> -I/export/home/drkirkby/sage-4.6.1.alpha2/devel/sage/sage/gsl/ >>> -I/export/home/drkirkby/.sage//temp/laptop/21516 >>> -I/export/home/drkirkby/sage-4.6.1.alpha2/local/include/python2.6 -c >>> _export_home_drkirkby__sage_temp_laptop_21516_tmp_2_pyx_0.c -o >>> build/temp.solaris-2.11-i86pc-2.6/_export_home_drkirkby__sage_temp_laptop_21516_tmp_2_pyx_0.o >>> -w -O2 >>> <BLANKLINE> >>> unable to execute gcc: No such file or directory >>> error: command 'gcc' failed with exit status 1 >>> <BLANKLINE> >>> ********************************************************************** >>> File >>> "/export/home/drkirkby/sage-4.6.1.alpha2/devel/sage/sage/misc/preparser.py", >>> line 1487: >>> sage: z >>> Expected: >>> -1 >>> Got: >>> 0 >>> ********************************************************************** >>> 1 items had failures: >>> 2 of 25 in __main__.example_20 >>> ***Test Failed*** 2 failures. >>> For whitespace errors, see the file >>> /export/home/drkirkby/.sage//tmp/.doctest_preparser.py >>> [11.7 s] >>> >>> ---------------------------------------------------------------------- >>> The following tests failed: >>> >>> sage -t -force_lib "devel/sage/sage/misc/preparser.py" >>> Total time for all tests: 11.7 seconds >>> >>> If a test can fail due to the lack of a compiler, does this mean that >>> to fully utilize a binary install of Sage, the system should have a >>> development system on it? >> >> This test should be marked optional, e.g., something like >> >> # optional - compiler >> >> or some other tag. > > Obviously I can create a patch and add "# optional - compiler" but is > there any guidance on what tags are used? How should I tag things?
There's some information in the Developer's Guide at http://www.sagemath.org/doc/developer/conventions.html#further-conventions-for-automated-testing-of-examples and a somewhat recent list of "optional" modifiers at http://groups.google.com/group/sage-devel/browse_thread/thread/69ddac6b90236a61/0455a95c3e9b410c?#0455a95c3e9b410c I think we already have some "gcc" optional tests in misc/cython.py and misc/session.pyx. > I appreciate "optional" means the test does not get run unless one > runs the optional tests, but beyond that I don't have a clue what else > should be written. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
