[Automated-testing] Automated testing update

[Iorga, Cristian]

Hello,
There might be a misunderstanding here...
The interactive SSH is not related to the EUT... is just a mean of controlling what serial output is collected at some point in time.
The serial line capture will be a per job solution, like you said, in order to make an association with a specific test, run and target.
At the moment, conmux is not integrated in our test lab.
It will be taken into consideration when we will start the tests.

Regards,
Cristian


-----Original Message-----
From: Darren Hart [mailto:dvhart at linux.intel.com] 
Sent: Wednesday, March 12, 2014 6:35 PM
To: Iorga, Cristian; Paul Eggleton
Cc: automated-testing at yoctoproject.org
Subject: Re: [Automated-testing] Automated testing update


Not if it doesn't boot :-) This is why things like autotest capture the serial console.

Setting up conmux is trivial, I'd suggest doing that.

The serial concentrator also has a mechanism to record the serial logs.
This isn't as good as a per job capture solution as it can be harder to find the right bit of log, but at least you would have it when needed.

To be blunt about it, any sort of Automated QA tooling / harness needs to have serial console boot logging integrated.

--
Darren

On 3/11/14, 22:40, "Iorga, Cristian" <cristian.iorga at intel.com> wrote:

>We can do that via the interactive SSH, but at the moment is not 
>integrated into the original expect script, as the purpose of the 
>script is to control the power to the board under test.
>I will discuss this with Stefan and come up with a solution; we had a 
>preliminary discussion on that, but the technical solution was not 
>implemented.
>
>Regards,
>Cristian Iorga
>YP
>Intel Corporation
>
>-----Original Message-----
>From: Darren Hart [mailto:dvhart at linux.intel.com]
>Sent: Wednesday, March 12, 2014 7:33 AM
>To: Iorga, Cristian; Paul Eggleton
>Cc: automated-testing at yoctoproject.org
>Subject: Re: [Automated-testing] Automated testing update
>
>On 3/11/14, 22:28, "Iorga, Cristian" <cristian.iorga at intel.com> wrote:
>
>>Hi Paul, Darren, all,
>>
>>The Python script is used to interact with the remote powerstrip.
>>An expect script and a solution specific to our test lab 
>>infrastructure is used together with the Python script.
>>The solution specific to the test lab is based on interactive SSH 
>>sessions, secured via the use of SSH keys.
>>The expect script interacts with interactive SSH, which interacts with 
>>the Python script.
>>
>>At this moment, conmux is not used in the setup, as it is not 
>>necessary for our test lab.
>
>How do you capture serial console logs for when boots fail or to 
>collect kernel messages?
>
>--
>Darren
>
>>
>>Regards,
>>Cristian Iorga
>>YP
>>Intel Corporation
>>
>>-----Original Message-----
>>From: Paul Eggleton [mailto:paul.eggleton at linux.intel.com]
>>Sent: Tuesday, March 11, 2014 7:08 PM
>>To: Darren Hart
>>Cc: Iorga, Cristian; automated-testing at yoctoproject.org
>>Subject: Re: [Automated-testing] Automated testing update
>>
>>On Tuesday 11 March 2014 09:47:26 Darren Hart wrote:
>>> On 3/11/14, 4:03, "Paul Eggleton" <paul.eggleton at linux.intel.com>
>>>wrote:
>>> >Cristian is working on an expect script for the power strip in the 
>>> >test rack that we have to be used in conjunction with 
>>> >conmux/hardreset for resetting boards.
>>> 
>>> Is this in addition to the python script I sent for interacting with 
>>> the power strip? Just want to make sure we're not duplicating effort.
>>
>>That's basically what I'm referring to; as far as I'm aware that's 
>>what Cristian is working with.
>>
>>Cheers,
>>Paul
>>
>>--
>>
>>Paul Eggleton
>>Intel Open Source Technology Centre
>>
>
>
>--
>Darren Hart
>Yocto Project - Linux Kernel
>Intel Open Source Technology Center
>
>
>
>
>


--
Darren Hart
Yocto Project - Linux Kernel
Intel Open Source Technology Center