Re: [sage-devel] Some cleanup of signal handling code (#13946) needs review

2013-01-13 Thread Johannes
Hi,
I run 'sage -tp 10 -long src/sage/src' (is there a better way to do a
test all?)
and a get a bunch of errors. Most of them coming from undefined
variables in the tests. I don't think that all these test are broken
(400+), because some of the errors look like the following one:

 File 
 /usr/lib/sagemath/devel/sage-dev/sage/combinat/rigged_configurations/kleber_tree.py,
  line 630:
 sage: KT.plot()
 Exception raised:
 Traceback (most recent call last):
   File /usr/lib/sagemath/local/bin/ncadoctest.py, line 1231, in 
 run_one_test
 self.run_one_example(test, example, filename, compileflags)
   File /usr/lib/sagemath/local/bin/sagedoctest.py, line 38, in 
 run_one_example
 OrigDocTestRunner.run_one_example(self, test, example, filename, 
 compileflags)
   File /usr/lib/sagemath/local/bin/ncadoctest.py, line 1172, in 
 run_one_example
 compileflags, 1) in test.globs
   File doctest __main__.example_18[4], line 1, in module
 KT.plot()###line 630:
 sage: KT.plot()
   File 
 /usr/lib/sagemath/local/lib/python/site-packages/sage/combinat/rigged_configurations/kleber_tree.py,
  line 633, in plot
 return self.digraph().plot(edge_labels=True, vertex_size=0, **options)
   File 
 /usr/lib/sagemath/local/lib/python/site-packages/sage/combinat/rigged_configurations/kleber_tree.py,
  line 617, in digraph
 if have_dot2tex():
   File 
 /usr/lib/sagemath/local/lib/python/site-packages/sage/graphs/dot2tex_utils.py,
  line 29, in have_dot2tex
 return dot2tex.dot2tex(graph {}, format = positions) == {}
   File 
 /usr/lib/sagemath/local/lib/python/site-packages/dot2tex/__init__.py, line 
 49, in dot2tex
 return d2t.convert_graph(dotsource,**kwargs)
   File 
 /usr/lib/sagemath/local/lib/python/site-packages/dot2tex/dot2tex.py, line 
 2966, in convert_graph
 tex = main(True, dotsource,options)
   File 
 /usr/lib/sagemath/local/lib/python/site-packages/dot2tex/dot2tex.py, line 
 2928, in main
 s =  conv.convert(dotdata)
   File 
 /usr/lib/sagemath/local/lib/python/site-packages/dot2tex/dot2tex.py, line 
 774, in convert
 sys.exit(1)
 SystemExit: 1


attached the list of failed tests.

bg,
Johannes

On 12.01.2013 16:38, Jeroen Demeyer wrote:
 Please review #13946, it does some misc cleanup of the signal handling
 code without changing its functionality.  It is mainly meant to provide
 a more solid base for future enhancements to the signal code:
 http://trac.sagemath.org/sage_trac/ticket/13946
 
 Thanks,
 Jeroen.
 

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
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.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.


sage -t -long src/sage/src/misc/benchmark.py # 2 doctests failed
sage -t -long src/sage/src/tests/benchmark.py # 1 doctests failed
sage -t -long src/sage/src/misc/functional.py # 1 doctests failed
sage -t -long src/sage/src/tests/book_stein_ent.py # 4 doctests failed
sage -t -long src/sage/src/databases/cremona.py # 57 doctests failed
sage -t -long src/sage/src/tests/cmdline.py # 2 doctests failed
sage -t -long src/sage/src/combinat/root_system/cartan_type.py # 6 
doctests failed
sage -t -long src/sage/src/combinat/tutorial.py # 1 doctests failed
sage -t -long src/sage/src/combinat/posets/hasse_diagram.py # 3 
doctests failed
sage -t -long src/sage/src/combinat/posets/linear_extensions.py # 10 
doctests failed
sage -t -long src/sage/src/combinat/posets/posets.py # 13 doctests 
failed
sage -t -long src/sage/src/combinat/crystals/spins.py # 64 doctests 
failed
sage -t -long src/sage/src/combinat/crystals/crystals.py # 20 doctests 
failed
sage -t -long src/sage/src/combinat/crystals/direct_sum.py # 40 
doctests failed
sage -t -long src/sage/src/combinat/crystals/affine.py # 131 doctests 
failed
sage -t -long src/sage/src/combinat/crystals/fast_crystals.py # 76 
doctests failed
sage -t -long src/sage/src/combinat/crystals/littelmann_path.py # 3 
doctests failed
sage -t -long src/sage/src/combinat/crystals/letters.py # 157 doctests 
failed
sage -t -long src/sage/src/combinat/crystals/tensor_product.py # 210 
doctests failed
sage -t -long src/sage/src/combinat/crystals/highest_weight_crystals.py 
# 63 doctests failed
sage -t -long src/sage/src/combinat/crystals/kirillov_reshetikhin.py # 
524 doctests failed
sage -t -long src/sage/src/combinat/crystals/alcove_path.py # 62 
doctests failed
sage -t -long 
src/sage/src/combinat/rigged_configurations/rigged_configuration_element.py # 2 
doctests failed
sage -t -long src/sage/src/combinat/rigged_configurations/bijection.py 
# 4 

Re: [sage-devel] Some cleanup of signal handling code (#13946) needs review

2013-01-13 Thread Volker Braun
On Sunday, January 13, 2013 11:27:09 AM UTC, Johhannes wrote:

 I run 'sage -tp 10 -long src/sage/src' (is there a better way to do a 
 test all?) 


Yes, make ptest / make ptestlong

and a get a bunch of errors. Most of them coming from undefined 
 variables in the tests


Do you have LaTeX installed? Some plot commands use it.


-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
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.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.




Re: [sage-devel] Some cleanup of signal handling code (#13946) needs review

2013-01-13 Thread Johannes
yea, I have and I never had problems with it. It's a big surprise for
me, that so much tests failed, even because I never recognized any problems.

bg,
Johannes

On 13.01.2013 12:44, Volker Braun wrote:
 On Sunday, January 13, 2013 11:27:09 AM UTC, Johhannes wrote:
 
 I run 'sage -tp 10 -long src/sage/src' (is there a better way to do a
 test all?)
 
 
 Yes, make ptest / make ptestlong
 
 and a get a bunch of errors. Most of them coming from undefined
 variables in the tests
 
 
 Do you have LaTeX installed? Some plot commands use it.
 
 
 -- 
 You received this message because you are subscribed to the Google
 Groups sage-devel group.
 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.
 Visit this group at http://groups.google.com/group/sage-devel?hl=en.
  
  

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
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.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.




Re: [sage-devel] Some cleanup of signal handling code (#13946) needs review

2013-01-13 Thread Johannes
I think something with my installation is broken, I removed the patch
and still get the same errors.
I try to track down the reasons for this.

bg,
Johannes

On 13.01.2013 19:49, Johannes wrote:
 yea, I have and I never had problems with it. It's a big surprise for
 me, that so much tests failed, even because I never recognized any problems.
 
 bg,
 Johannes
 
 On 13.01.2013 12:44, Volker Braun wrote:
 On Sunday, January 13, 2013 11:27:09 AM UTC, Johhannes wrote:

 I run 'sage -tp 10 -long src/sage/src' (is there a better way to do a
 test all?)


 Yes, make ptest / make ptestlong

 and a get a bunch of errors. Most of them coming from undefined
 variables in the tests


 Do you have LaTeX installed? Some plot commands use it.


 -- 
 You received this message because you are subscribed to the Google
 Groups sage-devel group.
 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.
 Visit this group at http://groups.google.com/group/sage-devel?hl=en.
  
  
 

-- 
You received this message because you are subscribed to the Google Groups 
sage-devel group.
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.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.