From: Kaushal Modi <kaushal.modi@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Probably broke the Worg build?
Date: Sat, 06 Jan 2018 02:54:39 +0000 [thread overview]
Message-ID: <CAFyQvY0yTb8iL9+212uFn0BtqU9HyN-wFvx_FHeURFbNfdb54g@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY19idwvdu6bG+2wDS+T1CCv6BRFnCeBMjeMNmTavTdcKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On Fri, Jan 5, 2018 at 9:05 PM Kaushal Modi <kaushal.modi@gmail.com> wrote:
>
> Thanks! I just pushed one more commit (
> https://code.orgmode.org/bzg/worg/commit/4feac9160363279653a3d19cf68619e6a9c02fee
> ).. let's see if that freezes up the build again.
>
My commits seem to have frozen Worg builds again.. sorry. But I don't know
what I am doing wrong.
I also noticed below, which should help debug this.
My "git push origin master" commands always "fail".. but they seem to work
i.e. the commits do reach the remote fine.
For example, this commit[1] got pushed fine, but the log shows this:
=====
Counting objects: 5, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 478 bytes | 478.00 KiB/s, done.
Total 5 (delta 4), reused 0 (delta 0)
error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504
Gateway Time-out
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
=====
[1]:
https://code.orgmode.org/bzg/worg/commit/397cb3c0bd0e33ba6b6522c28bf6fd0b3e461d04
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2031 bytes --]
next prev parent reply other threads:[~2018-01-06 2:54 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-28 17:12 [IMPORTANT] Server migration: please update your git repositories before 31/12/2017 Bastien Guerry
2017-12-29 7:32 ` Michael Welle
2017-12-29 12:23 ` Bastien Guerry
2017-12-29 9:59 ` Achim Gratz
2017-12-29 12:26 ` Bastien Guerry
2017-12-30 10:39 ` Allen Li
2017-12-30 11:23 ` Bastien
2017-12-30 11:39 ` Achim Gratz
2017-12-30 11:57 ` Bastien
2017-12-30 21:50 ` Allen Li
2017-12-31 8:53 ` Achim Gratz
2017-12-29 16:43 ` Bastien Guerry
2018-01-04 18:11 ` Achim Gratz
2018-01-04 18:44 ` Kaushal Modi
2018-01-04 18:50 ` Nicolas Goaziou
2018-01-04 18:52 ` Kaushal Modi
2018-01-05 17:31 ` Kaushal Modi
2018-01-05 17:47 ` Probably broke the Worg build? (Was: Re: [IMPORTANT] Server migration..) Kaushal Modi
2018-01-06 1:54 ` Probably broke the Worg build? Bastien
2018-01-06 2:05 ` Kaushal Modi
2018-01-06 2:54 ` Kaushal Modi [this message]
2018-01-04 19:21 ` [IMPORTANT] Server migration: please update your git repositories before 31/12/2017 Achim Gratz
2018-01-04 14:19 ` Kaushal Modi
2018-01-04 15:36 ` Nicolas Goaziou
2018-01-04 16:05 ` Kaushal Modi
2018-01-04 18:12 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY0yTb8iL9+212uFn0BtqU9HyN-wFvx_FHeURFbNfdb54g@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).