https://bugzilla.wikimedia.org/show_bug.cgi?id=59930

Antoine "hashar" Musso <has...@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Git/Gerrit                  |Continuous integration

--- Comment #4 from Antoine "hashar" Musso <has...@free.fr> ---
(In reply to comment #2)
> https://gerrit.wikimedia.org/r/103546 , again.
> 
> Can we please revert jenkins to when it worked?

That is unrelated to the upgrade of Zuul I did last week which is "simply" add
a middle war between Zuul and Jenkins: Gearman.

The timeout issue is not related to Gerrit since we do not use it. The changes
are fetched using something like:

git fetch \
  refs/zuul/master/Z0e1e8799e33145bc911d2bd465d59179 \
  git://zuul.eqiad.wmnet/mediawiki/core \
  --reference=/srv/ssd/gerrit/mediawiki/core.git


The URL git://zuul.eqiad.wmnet/mediawiki/core points to gallium server which
has the Zuul daemon. That is where the merge references are created.  They are
publishing using git-daemon.

The reference /srv/ssd/gerrit/mediawiki/core.git is a replication of git
repositories which is on the same disk as the jobs workspace (/srv/ssd).  Which
mean when cloning, git will use hardlinks and save a ton of network I/O and
disk space.


When the fetch occurs, the client side apparently send to the server
(git://zuul.eqiad.wmnet/) a list of all objects then a diff is made server side
and the missing elements are sent back to the client.

The timeouts might be caused when a new workspace is created which cause the
full repository to be sent to the client. Might end up taking longer than 10
minutes :/

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to