From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay1.mentorg.com ([192.94.38.131]) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1PI3Tl-0003JG-Ha for openembedded-devel@lists.openembedded.org; Mon, 15 Nov 2010 19:08:34 +0100 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1PI3Si-0005ug-O5 from Tom_Rini@mentor.com for openembedded-devel@lists.openembedded.org; Mon, 15 Nov 2010 10:07:28 -0800 Received: from na2-mail.mgc.mentorg.com ([134.86.114.213]) by svr-orw-fem-01.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 15 Nov 2010 10:07:25 -0800 Received: from [172.30.80.225] ([172.30.80.225]) by na2-mail.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 15 Nov 2010 11:07:25 -0700 Message-ID: <4CE176D9.6090903@mentor.com> Date: Mon, 15 Nov 2010 11:07:21 -0700 From: Tom Rini Organization: Mentor Graphics Corporation User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10 MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <4CE02C8A.2040002@mentor.com> In-Reply-To: X-OriginalArrivalTime: 15 Nov 2010 18:07:25.0495 (UTC) FILETIME=[F522F470:01CB84EF] X-SA-Exim-Connect-IP: 192.94.38.131 X-SA-Exim-Mail-From: Tom_Rini@mentor.com X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on discovery X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: Yes (on linuxtogo.org) Subject: Re: testing branch 2010-11-12 X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2010 18:08:34 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 11/15/2010 08:47 AM, Cliff Brake wrote: > On Sun, Nov 14, 2010 at 2:23 PM, Yury Bushmelev wrote: >> 2010/11/14 Tom Rini: >>> On 11/14/2010 11:11 AM, Frans Meulenbroeks wrote: >>>> >>>> 2010/11/12 Cliff Brake: >>>>> >>>>> testing-next is ready for clean builds. Not many builds succeeded >>>>> last week--I suspect people have been busy: >>>> >>>> Actually my builds also succeeded (apart from the neek one which seem >>>> to require some more love). The autobuilder did it's job quite nicely, >>>> but I was just not around to verify the results and update the page. >>>> The neek requires at least the os2 patch. >>>> >>>> Testing 2010-11-12 gives the same results. updated the testing page. >>> >>> After my first week of doing some testing branch test builds I was thinking, >>> would some form of either automated result submitting or form-based result >>> submitting be a good idea? We could try and use a google doc spreadsheet / >>> form, for example. Thoughts? >> >> I'll prefer to use our oestats-server to auto-publish builds data. >> Oestats have complete information about builds. > > If someone has the time to update the oestats-server to provide > summary data in a tabular form, that would be great. > > Alternatively, using forms on a google spreadsheet is an interesting > idea. I had not thought of forms as a way that we could get anonymous > build data with requiring a google account. Then again, I'm not sure > how we would keep the form from being spammed, other than perhaps > hiding it. I do have to admit that I hadn't given it more than a few seconds thought, but can't we perform some sanity checks on the input? That should really cut down on the spam, I would think (ie make sure the tested tag field starts with testing_). If this sounds like a possibly decent idea I can try and play with it a little bit. -- Tom Rini Mentor Graphics Corporation