Could anyone explain this message please. I tried to push some changes on family files to core but it hanged until I aborted the pushing. I did not found these changes on Gerrit. How to proceed in that matter?
Greetings xqt
----- Ursprüngliche Nachricht ----- Von: Travis CI Gesendet: 02.09.2013 19:38 An: info@gno.de Betreff: [Errored] wikimedia/pywikibot-core#114 (master - 5105954)
The build has errored.
Repository
wikimedia/pywikibot-core
Build #114
https://travis-ci.org/wikimedia/pywikibot-core/builds/10902770
Changeset
https://github.com/wikimedia/pywikibot-core/compare/da3542c8738c...5105954bd...
Commit
5105954 (master)
Message
update language_by_size from compat
Change-Id: Iffcfb52295a5bedda4c4748bd380ffda3a1343ff
Author
xqt
Duration
10 minutes and 25 seconds
You can configure recipients for build notifications in your configuration file. Further documentation about Travis CI can be found here. For help please join our IRC channel irc.freenode.net#travis.
Want Travis CI for your private repositories?
Powered by img { margin-right: 16px !important; }
Hi xqt,
On 3 September 2013 01:36, info@gno.de wrote:
Could anyone explain this message please. I tried to push some changes on family files to core but it hanged until I aborted the pushing. I did not found these changes on Gerrit. How to proceed in that matter?
This message is unrelated to the family files - it was caused by my commit ( https://github.com/wikimedia/pywikibot-core/commit/3e8885c3dd3fd50e57e3804d6...) which was +2ed by you. Before, it was jenkins-bot that was the author of merge commits -- apparently it's now the +2-er (which makes very little sense to me). Anyway - the mail should really have landed on *my* doorstep instead. I'll check with Ops to see if anything changed in the configuration.
Merlijn
----- Original Nachricht ---- Von: Merlijn van Deen valhallasw@arctus.nl An: Pywikipedia discussion list pywikipedia-l@lists.wikimedia.org Datum: 03.09.2013 09:53 Betreff: Re: [Pywikipedia-l] [Errored] wikimedia/pywikibot-core#114 (master - 5105954)
Hi xqt,
On 3 September 2013 01:36, info@gno.de wrote:
Could anyone explain this message please. I tried to push some changes on family files to core but it hanged until I aborted the pushing. I did not found these changes on Gerrit. How to proceed in that matter?
This message is unrelated to the family files - it was caused by my commit ( https://github.com/wikimedia/pywikibot-core/commit/3e8885c3dd3fd50e57e3804d6 9cd2e29894f0780) which was +2ed by you. Before, it was jenkins-bot that was the author of merge commits -- apparently it's now the +2-er (which makes very little sense to me). Anyway - the mail should really have landed on *my* doorstep instead. I'll check with Ops to see if anything changed in the configuration.
Merlijn
This is strange to me because the travis message is related to a commit that I tried to push to core. Look at that changeset: https://github.com/wikimedia/pywikibot-core/compare/da3542c8738c...5105954bd...
I see that diff on github but it is not places at core. Maybe the reason was that the push was hanging during transmission.
Greetings xqt
On 3 September 2013 12:53, info@gno.de wrote:
I see that diff on github but it is not places at core. Maybe the reason was that the push was hanging during transmission.
It seems the commit was pushed without going to code-review - this was possible because of a misconfiguration. Now direct pushes are blocked again, which means you would have gotten an error instead of an unclear situation.
Merlijn
On 3 September 2013 12:53, info@gno.de wrote:
I see that diff on github but it is not places at core. Maybe the reason was that the push was hanging during transmission.
It seems the commit was pushed without going to code-review - this was possible because of a misconfiguration. Now direct pushes are blocked again, which means you would have gotten an error instead of an unclear situation.
Merlijn
Yes I saw that change and I recognized that restriction in past. I played for the pushing options for my repos in past. The compat works most of the time but core did not. pushing to refs/for/master redirects it to refs/refs/for/master and I don't find the point. The local .git/config files are identical except of the external entries. It's enough to drive up the wall.
Greetings xqt