www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Henwood <Richard.Henw...@arm.com>
Subject RE: identifying builder target architecture?
Date Wed, 06 Jul 2016 18:24:57 GMT
Thanks for the prompt replies.

What I think I'm reading is that non-Linux-x86 targets cannot be relied upon today and as
such are a 'nice-to-have'. I assume the un-reliability issue is caused by a scarcity of build
experts who are already stretched thin keeping up with the huge demands of the Apache eco-system.
From reviewing the mail archives, it seems Dmitry from Microsoft started a related discussion
a few months ago [1] with a conclusion that the project could best fulfil it's needs outside
of the scope of builds.apache.org.

If a project wanted to avoid an external CI loop, what is the most useful thing a non-apache
person can contribute?

Best regards,

1. http://mail-archives.apache.org/mod_mbox/www-builds/201603.mbox/%3CBN3PR03MB13685317171A1F2EE8F8D6DED1B20%40BN3PR03MB1368.namprd03.prod.outlook.com%3E

-----Original Message-----
From: Allen Wittenauer [mailto:aw@apache.org]
Sent: Tuesday, July 05, 2016 9:49 AM
To: builds@apache.org
Subject: Re: identifying builder target architecture?

> On Jul 5, 2016, at 7:42 AM, Richard Henwood <Richard.Henwood@arm.com> wrote:
> So if you have any guidance here - or general advice how to pursue my investigations
- I would appreciate it.

When I start targeting a different set of boxes on the build infrastructure, I generally start
with a simple job that tells me the uname value, a few ls's, etc, to get the lay of the land
then go from there.

The problem is that the non-Linux-x86 machines always seem to be in various states of disrepair
and/or just flat out turned off so there's a bit of a reliability problem when targeting those
machines. :(  [Latest casualty appears to be the Mac OS X machine, turned off literally a
day after I got Hadoop build status published to the mailing lists.]

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may
also be privileged. If you are not the intended recipient, please notify the sender immediately
and do not disclose the contents to any other person, use it for any purpose, or store or
copy the information in any medium. Thank you.

View raw message