patchbot runs failing apply

58 views
Skip to first unread message

Ralf Stephan

unread,
Apr 28, 2014, 2:17:08 AM4/28/14
to sage-...@googlegroups.com
Several branches needing review and merging fine get an "ApplyFailed" ticket by
patchbot runners (many thanks for the service BTW). This is due to 


where there are workarounds. So please if you run a patchbot check your logs

It would be prudent to improve the instructions to no longer recommend installation
of patchbot-2.1.spkg but a newer spkg if it exists (it still doesn't).

Regards,

Nathann Cohen

unread,
Apr 28, 2014, 4:15:11 AM4/28/14
to sage-...@googlegroups.com
Yooooooooooooooooo !!!

 
Several branches needing review and merging fine get an "ApplyFailed" ticket by
patchbot runners (many thanks for the service BTW). This is due to 


where there are workarounds. So please if you run a patchbot check your logs

Yeah it's mine, sorry :-/ 

It would be prudent to improve the instructions to no longer recommend installation
of patchbot-2.1.spkg but a newer spkg if it exists (it still doesn't).

How on earth should a patchbot be installed ? I tried one thousand times to install one on my computer, and all it produces are those results or exceptions because of ccache which is already installed (and apparently it is a problem ....)

Nathann 

Nathann Cohen

unread,
Apr 28, 2014, 4:23:00 AM4/28/14
to Sage devel
....

Okay, I just installed a more recent version of the patchbot as it seems that "sage -i patchbot" installs an old one, and here is the new result :

patchbot@silence:~/sage$ ./sage -patchbot
Getting trusted author list...
WARNING: Assuming sage-main is pristine.
WARNING: Do not use this copy of sage while the patchbot is running.
git checkout base
Already on 'base'
git fetch git://github.com/sagemath/sage.git +master:upstream



============================== 0 ==============================
base
score None



Traceback (most recent call last):
  File "/home/patchbot/sage/local/bin/patchbot/patchbot.py", line 793, in <module>
    main(args)
  File "/home/patchbot/sage/local/bin/patchbot/patchbot.py", line 756, in main
    res = patchbot.test_a_ticket(0)
  File "/home/patchbot/sage/local/bin/patchbot/patchbot.py", line 412, in test_a_ticket
    self.report_ticket(ticket, status='Pending', log=None)
  File "/home/patchbot/sage/local/bin/patchbot/patchbot.py", line 666, in report_ticket
    report['git_branch'] = ticket['git_branch']
KeyError: 'git_branch'
patchbot@silence:~/sage$ 

.....

Nathann


--
You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-devel/GHMpjpAjmwA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-devel+...@googlegroups.com.
To post to this group, send email to sage-...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Volker Braun

unread,
Apr 28, 2014, 6:11:18 AM4/28/14
to sage-...@googlegroups.com
Whats the recommended way for running the git version of the patchbot? Just installing it manually? Maybe there is a better way?

Ralf Stephan

unread,
Apr 28, 2014, 8:27:04 AM4/28/14
to sage-...@googlegroups.com

Well if every release was tagged one could simply
point sage -I to the URL of the tarball that is automagically
created by github.

--

Robert Bradshaw

unread,
Apr 29, 2014, 4:00:57 AM4/29/14
to sage-devel
sage -i http://sage.math.washington.edu/home/robertwb/patches/patchbot-2.1.1.spkg

I've updated the instructions as well. I'm not sure what the best way
is to mix sage spkgs and a live repository--that has always been a
pain... Any ideas? (I suppose the spkg could go a git pull, but then
the version would not be accurately reflected...)
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an

Ralf Stephan

unread,
Apr 29, 2014, 6:38:55 AM4/29/14
to sage-...@googlegroups.com

If your git project would be named 'patchbot' instead of 'sage-patchbot' then every time you do a 'git tag' in your project a tarball with the right directory structure (I believe) is created on github. See project page / releases. This can then be installed via sage -I http...

Or any SPKG that is hosted on github.

http://trac.sagemath.org/ticket/16259

Regards,

You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-devel/GHMpjpAjmwA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-devel+...@googlegroups.com.

Niles Johnson

unread,
Apr 29, 2014, 12:00:26 PM4/29/14
to sage-...@googlegroups.com
I just started trying to run patchbot yesterday.  Even with the new spkg, I'm having trouble with either build failures or apply failures.  At least one of these was caused by forgetting to do 'make distclean && make' when switching from master to develop or vice versa.  

I had one successful run when I changed the patchbot base branch from master to develop, so I'm trying that again.  So far I've been focusing on just one ticket which is simple and which I know should apply cleanly and pass all tests.  If you want, you can see the my log outputs at

Robert Bradshaw

unread,
Apr 29, 2014, 5:44:57 PM4/29/14
to sage-devel
Oh, nice. I'll play with that.

Robert Bradshaw

unread,
Apr 29, 2014, 5:50:44 PM4/29/14
to sage-devel
The error looks like a legitimate build failure:

Setting up build directory for matplotlib-1.3.1
Finished set up
...
Traceback (most recent call last):
File "setup.py", line 10, in <module>
use_setuptools()
File "/tmp/tmpDP2B5q-sage-git-temp-16226/local/var/tmp/sage/build/matplotlib-1.3.1/src/distribute_setup.py",
line 180, in use_setuptools
download_delay)
File "/tmp/tmpDP2B5q-sage-git-temp-16226/local/var/tmp/sage/build/matplotlib-1.3.1/src/distribute_setup.py",
line 132, in _do_download
to_dir, download_delay)
File "/tmp/tmpDP2B5q-sage-git-temp-16226/local/var/tmp/sage/build/matplotlib-1.3.1/src/distribute_setup.py",
line 212, in download_setuptools
src = urlopen(url)
File "/home/johnson.5320/patchbot/local/lib/python2.7/urllib2.py",
line 127, in urlopen
return _opener.open(url, data, timeout)
File "/home/johnson.5320/patchbot/local/lib/python2.7/urllib2.py",
line 404, in open
response = self._open(req, data)
File "/home/johnson.5320/patchbot/local/lib/python2.7/urllib2.py",
line 422, in _open
'_open', req)
File "/home/johnson.5320/patchbot/local/lib/python2.7/urllib2.py",
line 382, in _call_chain
result = func(*args)
File "/home/johnson.5320/patchbot/local/lib/python2.7/urllib2.py",
line 1214, in http_open
return self.do_open(httplib.HTTPConnection, req)
File "/home/johnson.5320/patchbot/local/lib/python2.7/urllib2.py",
line 1184, in do_open
raise URLError(err)
urllib2.URLError: <urlopen error [Errno 110] Connection timed out>
Error building matplotlib package.

real 1m3.381s
user 0m0.171s
sys 0m0.194s
************************************************************************
Error installing package matplotlib-1.3.1
************************************************************************

IMHO, make should work without a network connection.
Reply all
Reply to author
Forward
0 new messages