Here are 2 distinct problems, that look similar.
(1) The new trac seems to have broken the patchbots, with the following
traceback. Maybe just because of https, but not sure.
Traceback (most recent call last):
File "sage_patchbot/patchbot.py", line 997, in test_a_ticket
File "sage_patchbot/trac.py", line 297, in pull_from_trac
File "sage_patchbot/trac.py", line 116, in scrape
File "sage_patchbot/trac.py", line 376, in load
File "sage_patchbot/trac_ticket.py", line 160, in TracTicket
File "/usr/lib/python2.7/xmlrpclib.py", line 1233, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.7/xmlrpclib.py", line 1587, in __request
verbose=self.__verbose
File "/usr/lib/python2.7/xmlrpclib.py", line 1273, in request
return self.single_request(host, handler, request_body, verbose)
File "sage_patchbot/digest_transport_py2.py", line 116, in single_request
File "/usr/lib/python2.7/xmlrpclib.py", line 1482, in parse_response
return u.close()
File "/usr/lib/python2.7/xmlrpclib.py", line 792, in close
raise ResponseError()
ResponseError: ResponseError()
2016-06-22 17:12:01
2 seconds
[2016-06-22 17:12:03] #20629 raises an exception: ResponseError()
Traceback (most recent call last):
File "sage_patchbot/patchbot.py", line 997, in test_a_ticket
File "sage_patchbot/trac.py", line 297, in pull_from_trac
File "sage_patchbot/trac.py", line 116, in scrape
File "sage_patchbot/trac.py", line 376, in load
File "sage_patchbot/trac_ticket.py", line 160, in TracTicket
File "/usr/lib/python2.7/xmlrpclib.py", line 1233, in __call__
return self.__send(self.__name, args)
File "/usr/lib/python2.7/xmlrpclib.py", line 1587, in __request
verbose=self.__verbose
File "/usr/lib/python2.7/xmlrpclib.py", line 1273, in request
return self.single_request(host, handler, request_body, verbose)
File "sage_patchbot/digest_transport_py2.py", line 116, in single_request
File "/usr/lib/python2.7/xmlrpclib.py", line 1482, in parse_response
return u.close()
File "/usr/lib/python2.7/xmlrpclib.py", line 792, in close
raise ResponseError()
ResponseError: ResponseError()
(2) when pushing using git push trac, it worked with the following similar
warning:
remote: Traceback (most recent call last):
remote: File "./hooks/post-receive.d/01-trac_branch", line 180, in
<module>
remote: for number, ticket in trac.ticket_iter(branch):
remote: File "./hooks/post-receive.d/01-trac_branch", line 75, in
ticket_iter
remote: for result in self.rpc.search.branch(branch):
remote: File "/usr/lib/python2.7/xmlrpclib.py", line 1233, in __call__
remote: return self.__send(self.__name, args)
remote: File "/usr/lib/python2.7/xmlrpclib.py", line 1587, in __request
remote: verbose=self.__verbose
remote: File "/usr/lib/python2.7/xmlrpclib.py", line 1273, in request
remote: return self.single_request(host, handler, request_body, verbose)
remote: File
"/srv/git/repositories/sage.git/hooks/post-receive.d/digest_transport.py",
line 154, in single_request
remote: return self.parse_response(response)
remote: File "/usr/lib/python2.7/xmlrpclib.py", line 1482, in
parse_response
remote: return u.close()
remote: File "/usr/lib/python2.7/xmlrpclib.py", line 792, in close
remote: raise ResponseError()
remote: xmlrpclib.ResponseError: ResponseError()
Le lundi 20 juin 2016 17:18:49 UTC+2, Erik Bray a écrit :
>
> Hi all,
>
> As decided toward the end of another recent thread [1] I willl be
> taking down the server at UW which hosts both trac.sagemath.org and
> git.sagemath.org, starting around 8:00 A.M. CEST. There are at least
> three reasons for this:
>
> 1. Mitigate issues related to reliance upon university IT
> infrastructure over which we have little control [2][3] or influence
> 2. Move to tier 1 cloud-based hosting for greater ease of deployment
> and (hopefully) better reliability
> 3. Address current and ongoing preformance / access issues with the
> Trac site, which are possibly related to 1
>
> An additional change to be aware of is that access to
> trac.sagemath.org, as well as the git web interface at
> git.sagemath.org will be switched to HTTPS *only*. HTTP redirects
> will be set up, but please update any URLs nonetheless.
>
> Other than that, with a little luck you should notice few or any
> differences. Please keep in mind though that the current Sage Trac
> infrastructure has a layer of grime and mold over it, and it's
> entirely possible I've missed a few spots while shining it up. So if
> anything isn't working after the migration please be patient and
> cooperate by sending notice either to
> sagemat...@googlegroups.com <javascript:>, or to me personally*.
>
> Best,
> Erik
>
> * The offer to e-mail me personally about such issues expires some
> indeterminate amount of time after the migration is completed. I want
> to be on-call for migration-related issues, but in general support
> issues should be sent to one of the mailing lists where they can be
> handled by the best personal available at the moment.
>
> [1] https://groups.google.com/d/msg/sage-devel/EKhgXsdKMhY/52fKpHDBAQAJ
> [2] https://groups.google.com/d/msg/sage-devel/Xw6CNq1lyiI/aeyT5TluDQAJ
> [3] https://groups.google.com/d/msg/sage-devel/Xw6CNq1lyiI/APzgctSUDQAJ
>
--
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 email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
