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
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
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/Linarohttp://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
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
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
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
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
