2011/5/4 Stefan Behnel <stefan...@behnel.de>: > Vitja Makarov, 04.05.2011 21:14: >> >> 2011/5/4 Stefan Behnel: >>> >>> Vitja Makarov, 04.05.2011 07:09: >>>> >>>> Jenkins doesn't work for me. It seems that it can't do pull and is >>>> running tests again obsolete sources. >>>> May be because of forced push. >>>> >>>> There are only 6 errors here: >>>> >>>> >>>> https://sage.math.washington.edu:8091/hudson/view/cython-vitek/job/cython-vitek-tests-py27-c/ >>> >>> According to the build logs of the sdist job, it was previously checking >>> out >>> the "master" branch and it seems you reconfigured it to use the >>> "unreachable_code" branch now. At least the recent checkouts have used >>> the >>> latest snapshot of the branches, so ISTM that everything is working >>> correctly. Could you point me to a build where something was going wrong >>> for >>> you? >> >> I've added the following line to sdist target >> >> +rm -fr $WORKSPACE/dist >> $WORKSPACE/python/bin/python setup.py clean sdist --formats=gztar >> --cython-profile --no-cython-compile >> >> Hope that should help, that's the only difference between >> cython-devel-sdist and cython-vitek-sdist. >> >> >> See here: >> >> https://sage.math.washington.edu:8091/hudson/view/cython-vitek/job/cython-vitek-tests-py27-c/166/ >> >> You can't find w_unreachable in the logs, it seems that cython code >> there is outdated. > > Ah, right, that's it. You can see the problem here: > > https://sage.math.washington.edu:8091/hudson/job/cython-vitek-sdist/97/artifact/dist/Cython-0.14+.tar.gz/*fingerprint*/ > > It's been using the 0.14+ sdist for ages instead of the 0.14.1+ one. > > That could also explain why your CPython regression tests are running much > faster than in cython-devel. >
Ok, so I should take a look at pyregr tests closer. -- vitja. _______________________________________________ cython-devel mailing list cython-devel@python.org http://mail.python.org/mailman/listinfo/cython-devel
