On Wed, 2011-05-04 at 10:35 +0400, Vitja Makarov wrote:

...

Can you please provide me jenkins account and I'll try to fix the issues myself?

It's better to use:

$ git fetch origin $ git checkout -f origin/master

Instead of git pull

Or $ git fetch origin $ git reset --hard origin/master which is what we used for our buildbot. -- Sincerely yours, Yury V. Zaytsev

On Wed, 2011-05-04 at 22:43 +0400, Vitja Makarov wrote:

Thanks! Am I right: when you do reset '--hard origin/master' you are on the master branch and when you do checkout you are in a 'detached state'?

Yes, I think that you are right, that's why we used to do reset instead: $ git fetch origin $ git checkout master $ git reset --hard origin/master By the way, you can also do $ git clean -dfx to make sure that EVERYTHING that doesn't belong to the tree is plainly wiped out (don't do that on your real checkouts unless you definitively have nothing to lose).

But it seems to me that the problem is somewhere in the jenkins configuration.

I didn't mean to say that there's no problem with Jenkins, just wanted to suggest a possibly better way of updating the CI checkout :-) -- Sincerely yours, Yury V. Zaytsev

2011/5/4 Stefan Behnel <stefan_ml@behnel.de>:

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-vi...

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?

Stefan

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-vi... You can't find w_unreachable in the logs, it seems that cython code there is outdated. -- vitja.

2011/5/4 Stefan Behnel <stefan_ml@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-vi...

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-vi...

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/artif...

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.