2011/5/29 Vitja Makarov <vitja.makarov@gmail.com>:
2011/5/29 Stefan Behnel <stefan_ml@behnel.de>:
Vitja Makarov, 29.05.2011 11:17:
2011/5/29 Stefan Behnel:
Vitja Makarov, 29.05.2011 10:11:
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.
Ah, sorry. I added you to the project members.
Btw there is one more commit in control_flow_fixes branch with few new tests.
That makes a good test for your write access then. ;)
Thanks. I've successfully pushed my changes. I removed old ControlFlow stuff completely.
What about "Error running command, failed with status 256." lines in sage build log? Is that cython crash?
Don't think so. Not sure what those failures are, but given that some modules fail to compile, maybe it's just the late result of such a build failure.
I see sigsegv in lxml tests: 1222/1364 ( 89.6%): test_xmlschema_import_file (lxml.tests.test_xmlschema.ETreeXMLSchemaTestCase) ... Segmentation fault https://sage.math.washington.edu:8091/hudson/job/cython-devel-lxml-trunk-py2... Is that control flow related issue? -- vitja.