[Development] Gerrit problems fixed (?)
tuukka.turunen at qt.io
Fri Dec 22 13:22:39 CET 2017
From: Tony Sarajärvi <tony.sarajarvi at qt.io>
Date: Friday, 22 December 2017 at 9.40
To: "development at qt-project.org" <development at qt-project.org>
Subject: Gerrit problems fixed (?)
The gerrit problems we’ve seen (example below (pardon for top posting with Outlook)) are potentially fixed. The problem was found to be in the AWS VM. Following actions were made to remedy the situation:
- Port range increased to allow more connections
- Mount options adjusted optimizing file access
- I/O scheduler is now ‘noop’
With these changes the symptoms are for now gone. If they start appearing again, just hit reply to this thread and let’s see if we can reproduce and fix it.
From: Tony Sarajärvi
Sent: keskiviikko 13. joulukuuta 2017 21.39
To: 'development at qt-project.org' <development at qt-project.org>
Subject: RE: Builds missing qmake?
Should have told you this as well. When you see this error message coming from the CI:
“Could not access requested repository (: RAN: /usr/bin/git --git-dir=/home/vmbuilder/ci-working-dir/git-repos/qt-project/qt/qtwebview --no-pager fetch --tags origin +refs/builds/qtci/5.9/1513182815:refs/builds/qtci/5.9/1513182815 STDOUT: packet_write_wait: Connection to 22.214.171.124 port 29418: Broken pipe fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. STDERR:”
It means that Coin is unable to retrieve needed sources from codereview. Again, as of now we don’t know the root cause for this. We can produce this even outside Coin, so it’s a problem outside our CI. We are investigating where and why the connections are lost.
When this happens you don’t have to contact us however. Just restage your commit and the next time around the sources might be retrieved.
I apologize for the inconvenience
From: Tony Sarajärvi
Sent: keskiviikko 13. joulukuuta 2017 11.26
To: 'development at qt-project.org' <development at qt-project.org<mailto:development at qt-project.org>>
Subject: Builds missing qmake?
If you stumble upon a problem in your build where the error message says that it can’t find qmake, contact us maintaining the CI immediately. It’s not a random failure in such that it goes away by restaging a few times. It means that for some reason (still unclear) we have a pointer indicating where the binaries should be, but they aren’t. So they are never even uncompressed. But we can’t really fail the build on missing artifacts, since we have no way of knowing if those binaries are optional or not. The error above clearly says that qtbase binaries are now uncompressed, hence the missing qmake, but we don’t want to hard code all the really dependent packages for every module. Instead, we’re trying to figure out why those binaries are missing in the first place.
So, qmake missing error -> contact us. We are needed to fix it currently.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development