linaro-validation November 2012

linaro-validation@lists.linaro.org

17 participants
58 discussions

Planning for the upgrade of control to 12.04 LTS

by Michael Hudson-Doyle

I've started a google doc on this subject: https://docs.google.com/a/linaro.org/document/d/1K_FrpM0qaDCKd6fRHyt_NDf10l… Team members, feel free to edit as appropriate. Anyone else with thoughts can add comments. Cheers, mwh

13 years, 8 months

USB Sound Card

by Dave Pigott

Hi all, I'm purchasing a dedicated server for the new dispatcher work, and also getting a USB sound card, as discussed at Connect. I'm looking for guidance as to functionality - a link to amazon would be quite helpful. :) Any suggestions welcome. Thanks Dave

13 years, 9 months

test / test case management in LAVA

by Michael Hudson-Doyle

We're going to be talking about test case management in LAVA at the Connect. I've brain-dumped some of my thoughts here: https://wiki.linaro.org/Platform/LAVA/Specs/TestCaseManagement Comments welcome. But if all you do is read it before coming to the session, that's enough for me :-) Cheers, mwh

13 years, 9 months

(Big) Results publishing from LAVA tests (security aspects)

by Paul Sokolovsky

Hello Validation team, Proceeding further with CBuild/LAVA integration work, it's time to think how to publish gcc, etc. binary tarballs as produced by the builds. Initially it seemed like an easy step, but the more I think about it, the more it seems like complicated to do "right". The tarballs in question are ~100Mb, so I guess there cannot be talk about publishing them as attachment to a result bundle. Let me know if that's ok though, because it would resolve all complexities below. Otherwise, is there a way to set some custom data per user, which would be available to all jobs submitted by that user - in a secure manner? The idea, that would be an access credential to use for publishing (so far we usually use SSH privkey to auth to publishing host). If not, is there a way to pass such information during job submission, but again in a secure manner (i.e. it shouldn't be part of job definition, as that's dumped in plain text). Any other infrastructure in LAVA (like, pre-authed publishing host) or suggestions how to solve this? Thanks, Paul Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog

13 years, 10 months

Health failure

by Dave Pigott

No joke. As I sent the last e-mail, another board failed: ------------ origen03 ------------ http://validation.linaro.org/lava-server/scheduler/job/40335 Looks like serial line corruption when we were trying to deploy the Android test image, so commands failed. Put back online to retest. Dave

13 years, 10 months

the magic lava job

by Andy Doan

Good news - my email alerts work! Bad news - I've just discovered a LAVA bug that was keep all our panda jobs from running: http://validation.linaro.org/lava-server/scheduler/job/40330/definition This job basically has a bad "server" parameter for the "submit_results_on_host" action. It causes the stack trace attached at the bottom. And the scheduler will keep trying over and over to run this. Its late and I must sleep, but can someone please take a look at this and propose a fix ASAP? Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 525, in __bootstrap self.__bootstrap_inner() File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 505, in run self.__target(*self.__args, **self.__kwargs) --- <exception caught here> --- File "/srv/lava/.cache/eggs/Twisted-12.1.0-py2.7-linux-x86_64.egg/twisted/python/threadpool.py", line 167, in _worker result = context.call(ctx, function, *args, **kwargs) File "/srv/lava/.cache/eggs/Twisted-12.1.0-py2.7-linux-x86_64.egg/twisted/python/context.py", line 118, in callWithContext return self.currentContext().callWithContext(ctx, func, *args, **kw) File "/srv/lava/.cache/eggs/Twisted-12.1.0-py2.7-linux-x86_64.egg/twisted/python/context.py", line 81, in callWithContext return func(*args,**kw) File "/srv/lava/.cache/eggs/lava_scheduler-0.24-py2.7.egg/lava_scheduler_daemon/dbjobsource.py", line 64, in wrapper return func(*args, **kw) File "/srv/lava/.cache/eggs/lava_scheduler-0.24-py2.7.egg/lava_scheduler_daemon/dbjobsource.py", line 211, in getJobForBoard_impl json_data = self._get_json_data(job) File "/srv/lava/.cache/eggs/lava_scheduler-0.24-py2.7.egg/lava_scheduler_daemon/dbjobsource.py", line 107, in _get_json_data netloc = job.submitter.username + '@' + parsed.hostname exceptions.TypeError: coercing to Unicode: need string or buffer, NoneType found

13 years, 10 months

Health check failures

by Dave Pigott

Just the one: ---------------- snowball07 ---------------- http://validation.linaro.org/lava-server/scheduler/job/40303 Timed out in booting the test image, but in an odd way. It issued the "mmc init" at the u-boot prompt, got a u-boot prompt back, and then timed out 5 minutes later without issuing the rest of the boot commands. Have put back online to retest. I'd suggest that rebooting the test image *might* have solved this. Either that, or a bug in LAVA has been unearthed. Thanks Dave

13 years, 10 months

Stuck jobs

by Dave Pigott

All on snowballs this time. Some have been stuck for 3 days. ---------------- snowball02 ---------------- http://validation.linaro.org/lava-server/scheduler/job/40045 The usual story. Pushed bundle, and then stuck. Did a cancel and kill -2 ---------------- snowball03 ---------------- http://validation.linaro.org/lava-server/scheduler/job/40221 Bit of an odd one. Running a health check, but it never even started executing. Did a cancel, but then couldn't find a process on control to match it. Went into admin and forced board offline, then back online and it started running a health check. Trouble is, it's still showing up as a long running job. :-/ ---------------- snowball04 ---------------- http://validation.linaro.org/lava-server/scheduler/job/40219/log_file Same story as snowball03, 07 and 08. ---------------- snowball05 ---------------- http://validation.linaro.org/lava-server/scheduler/job/39987 The usual story. Pushed bundle, and then stuck. Did a cancel and kill -2 ---------------- snowball06 ---------------- http://validation.linaro.org/lava-server/scheduler/job/40079 The usual story. Pushed bundle, and then stuck. Did a cancel and kill -2 ---------------- snowball07 ---------------- http://validation.linaro.org/lava-server/scheduler/job/40220 Same story as snowball03, 04 and 08. ---------------- snowball08 ---------------- http://validation.linaro.org/lava-server/scheduler/job/40218 Same story as snowball03, 04 and 07.

13 years, 10 months

LAVA health

by Dave Pigott

No overnight failures! \o/ And: http://validation.linaro.org/lava-server/scheduler/reports We've gone over 99% success in the last week for the first time ever. Excellent. Dave

13 years, 10 months

Health check status

by Dave Pigott

Hi all, One overnight failure: ---------------- panda-es04 ---------------- http://validation.linaro.org/lava-server/scheduler/job/40109 Failed to get into test image. Some sort of corruption. Went onto the board and booted test image again. It came up, and we got a command prompt, but it was still pretty flakey: https://pastebin.linaro.org/1129/ Although a reboot of the test image *might* have fixed this, it looks like either the test image was dodgy, or the board is genuinely failing. I've put back online to test. Thanks Dave

13 years, 10 months

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

linaro-validation November 2012