[Development] Builds failing due to android host

Thu May 23 12:21:05 CEST 2013

Yes we have. We call it the 'dev-ci' side, short for development. We've cloned a few machines from the CI to the dev-ci side, and also have gerrit, testresults-server etc duplicated with bogus data. However, small things and commits done by others than the CI team tend to get pushed directly to the CI, even though we shouldn't have. We will be more strict about this in the future, so that even small things which we think should always pass, are always ran through the dev-ci.

-Tony

From: Roscher-Nielsen Nils Christian
Sent: 23. toukokuuta 2013 13:19
To: Shaw Andy; Sarajärvi Tony; development at qt-project.org
Subject: RE: Builds failing due to android host

Hi,

Do we have something like a production and a test environment, so that we can push changes, updates, upgrades etc. to the test environment to see if it works, before using it in production? Realistically things will fail more often than we hope, and as Tony say, there is usually something waiting in the queue.. Or do we not have enough HW etc. to realistically do this?

I know we do this for other of our internal tools, but they might be less "complicated". Is it an idea worth investigating (when we have the time :) )

Best regards
Nils Christian Roscher-Nielsen

Sales Engineer - Digia, Qt

Visit us on: http://qt.digia.com<http://qt.digia.com/>

From: development-bounces+nils.roscher-nielsen=digia.com at qt-project.org [mailto:development-bounces+nils.roscher-nielsen=digia.com at qt-project.org] On Behalf Of Shaw Andy
Sent: 22. mai 2013 11:54
To: Sarajärvi Tony; development at qt-project.org
Subject: Re: [Development] Builds failing due to android host

I grant you that we are always releasing something, but in this instance I was referring to the fact that 5.1 beta is already out, with the final due in just a few weeks and time is running short because of the timing of that then it might be best to hold off on doing some upgrades until a generally more safer time. As such now the merge from stable to release as to wait because of the CI trouble, which puts more pressure on the actual schedule.

Andy

From: Sarajärvi Tony
Sent: 22. mai 2013 11:45
To: Shaw Andy; development at qt-project.org
Subject: RE: Builds failing due to android host

Do we ever have a situation that something is not "late into a release process"? If it's not 5.1, it's 5.1.1, or 5.2 beta, or 5.2 RC, or 5.2.1...  not to mention our 4.x builds :)

-Tony

From: Shaw Andy
Sent: 22. toukokuuta 2013 12:42
To: Sarajärvi Tony; development at qt-project.org
Subject: RE: Builds failing due to android host

That doesn't make it a valid thing to still do, testing or not. I am not sure what others think but do we want to still do upgrades to things on CI this late into a release process?

Andy

From: Sarajärvi Tony
Sent: 22. mai 2013 10:54
To: Shaw Andy; development at qt-project.org
Subject: RE: Builds failing due to android host

We have always something coming ;) And we didn't realize that this could cause problems. We got a request to update the tool chain and we just did as requested. We should have tested this on the dev side, but we don't have the luxury of time on our side. From now on, we don't upgrade or update anything before verifying on the dev side.

-Tony

From: Shaw Andy
Sent: 22. toukokuuta 2013 11:32
To: Sarajärvi Tony; development at qt-project.org
Subject: RE: Builds failing due to android host

Maybe I missed something, but why are upgrades like this being done in the middle of a release cycle? With Qt 5.1 final due in not too long then shouldn't these kind of upgrades wait until after the final release in order to avoid this sort of thing being a problem for the release?

Andy

From: development-bounces+andy.shaw=digia.com at qt-project.org [mailto:development-bounces+andy.shaw=digia.com at qt-project.org] On Behalf Of Sarajärvi Tony
Sent: 22. mai 2013 10:27
To: development at qt-project.org
Subject: Re: [Development] Builds failing due to android host

Updating the NDK began causing new and new problems, so Android builds are marked as 'forcesuccess' for the time being.

Regards,
-Tony

From: Sarajärvi Tony
Sent: 21. toukokuuta 2013 13:07
To: development at qt-project.org
Subject: Builds failing due to android host

Hi

If your build failed due to this message "Can not detect the android host. Please use -android-ndk-host option to specify one" you can just safely restage it. We made changes to our Puppet configuration regarding Androids, and yes, the CI team caused this fail.

We have a small known problem with Puppet, that currently running builds don't prevent Puppet from running.
Due to this, Puppet could potentially remove compile tools from under the build. Also, when a build finishes, it reboots the machine. This reboot kills the Puppet process and everything it was doing currently. This is most likely what happened to Android tools. They were being upgraded to 64 bit tools, and on some machines Puppet was killed during this process.

It will automatically retry in 90 minutes (which is Puppet's current timeout). Thus at some point it will fix itself.

We have a change for this already inbound so that Puppet doesn't do this, but it's been incoming since February, so don't hold your breath ;)

-Tony

Tony Sarajärvi
Senior Software Designer
Digia, Qt

Digia Plc
Elektroniikkatie 10
FI-90590 Oulu

Email: tony.sarajarvi at digia.com<mailto:tony.sarajarvi at digia.com>
Mobile: +358 050 482 1416
http://qt.digia.com
| Blog<http://blog.digia.com/> | Twitter<https://twitter.com/digiaonline> | LinkedIn<http://www.linkedin.com/company/5119> | YouTube<http://www.youtube.com/digiaonline> | Facebook<http://www.facebook.com/digiaonline> |
------------------------------------------------------------------
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error, please contact the sender immediately and delete the message and any attachments accompanying it. Digia Plc does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message.
------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20130523/4bf1565b/attachment.html>