2011/5/29 Stefan Behnel <stefan...@behnel.de>: > Vitja Makarov, 29.05.2011 10:11: >> >> 2011/5/28 Stefan Behnel: >>> >>> Stefan Behnel, 28.05.2011 18:06: >>>> >>>> Let's see how much of Sage we break. >>> >>> ... quite a bit. From a superficial glance, there seem to be some real >>> bugs, > > Bugs in Sage, to be clear. >
Ok. > >>> but most of the failures and warnings are most likely just uninitialised >>> variables that are expected to be None. >>> >>> >>> https://sage.math.washington.edu:8091/hudson/view/All/job/sage-build/740/consoleFull >> >> >> I've started new branch called control_flow_fixes. > > I think you can safely apply the subsequent fixes to the master branch, now > that the feature is in. That will also give you broader feedback from > Jenkins. > > I don't have write access to upstream repo. Btw there is one more commit in control_flow_fixes branch with few new tests. >> I've fixed the issue with RaiseStatNode. And unused variables that >> were not assigned or referenced now you get correct message. > > Cool. > What about "Error running command, failed with status 256." lines in sage build log? Is that cython crash? -- vitja. _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
