[Fuego] UART Alpha, Add New Test Suite to Fuego Dashboard

[Fuego] UART Alpha, Add New Test Suite to Fuego Dashboard

[dhinakar k]

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

Hi Tim,

UART Alpha Version
************************
I have to demo Fuego to my management on one of our target board.
The target board has only UART Connectivity. I have two weeks to
setup target (along with cross compiler, config files etc.) and demo
the LTP test suite execution on it. LTP is already in the Pre-packed test
list.
Should I be porting it again to my target to make it work? How big an
effort will it be?
Also can I get the alpha version of UART so that I can use it for this demo?

Adding a new test suite
***************************
1. Is there any plan to add LTP-DDT test suite into Fuego container?
2. If I want to add my own test suite or test to Fuego dashboard, what is
the process?
3. Is the dashboard customizable?

Please let me know.

Regards,
Dhinakar

[-- Attachment #2: Type: text/html, Size: 1048 bytes --]

Re: [Fuego] UART Alpha, Add New Test Suite to Fuego Dashboard

[Bird, Timothy]

See answers inline below.

> -----Original Message-----
> From: dhinakar k on Friday, March 31, 2017 1:46 AM
> Hi Tim,
> 
> UART Alpha Version
> ************************
> I have to demo Fuego to my management on one of our target board.
> The target board has only UART Connectivity. I have two weeks to
> setup target (along with cross compiler, config files etc.) and demo
> the LTP test suite execution on it. LTP is already in the Pre-packed test list.
> Should I be porting it again to my target to make it work?
No.  What you do it add your toolchain to Fuego, and Fuego will build
LTP for your target.  You can find instructions for adding a toolchain at:
http://bird.org/fuego/Adding_a_toolchain

Can you say where you are getting your toolchain from, and what kind it is?
(e.g. from Linaro, from your SoC vendor, from Debian packages, or building it yourself with
crosstool or Yocto Project or Buildroot?)

>How big an effort  will it be?
If you were not using serial, it should be trivial.  However, one outstanding
issue with the serial support is that it is not fast at transferring data.
Our configuration of LTP requires transferring about 450mg of data, which
takes too long over a serial port.  We have some sub-test configurations
for LTP, that require less space.  I haven't measured them to see how much
space they need on the target board.

LTP can be refactored to have a smaller footprint, but this would require
some work.

In your case, I would be interested to hear how the device filesystem is populated
now, and what size you have available for testing.  We might be able to customize
a test spec to use a subset of LTP that would work for your device.

> Also can I get the alpha version of UART so that I can use it for this demo?
 Yes.  Everything needed for using the serial port as a transport option
is included in my 'next' branch (and will be in the upcoming 1.1 release).
I hope to release 1.1-rc1 today or Monday.  Serial support will be included in
that release.

> Adding a new test suite
> ***************************
> 1. Is there any plan to add LTP-DDT test suite into Fuego container?
There were no prior plans to do this, but it looks like an interesting suite to add.
Since we have LTP, and LTP-DDT is a derivative, it should be relatively easy to 
add the individual tests from LTP.

> 2. If I want to add my own test suite or test to Fuego dashboard, what is the
> process?
Please see this page:
http://bird.org/fuego/Adding_a_test

> 3. Is the dashboard customizable?
Yes.  The Jenkins dashboard is extremely customizable, and there are numerous
view options and plugins to configure how you want the dashboard to look.
JTA and Fuego 1.0 used a lot of these plugins to create a specific look.
Fuego 1.1 leaves this more as an exercise for the user, since each site may want
their own Jenkins interface customizations.  We try to require a minimal set
of Jenkins plugins for Fuego core functionality.  Then, individual users and sites
can choose which of the Jenkins plugins to use for the dashboard look they want.

> 
> Please let me know.

There would be some work involved to make existing LTP work over the serial
port for your board.  But it should not be too difficult. More critical is how your
distribution of Linux is configured to initialize.  Does your board come up to a login
prompt, or directly into a shell prompt?

Let me know the answers to my questions, and we can work from there.

Regards,
 -- Tim

Re: [Fuego] UART Alpha, Add New Test Suite to Fuego Dashboard

[dhinakar k]

[-- Attachment #1: Type: text/plain, Size: 4790 bytes --]

Hi Tim,

Thanks a lot for your detailed reply.
Please find my comments inline.

Regards,
Dhinakar

On Sat, Apr 1, 2017 at 11:52 AM, Bird, Timothy <Tim.Bird@sony.com> wrote:

> See answers inline below.
>
> > -----Original Message-----
> > From: dhinakar k on Friday, March 31, 2017 1:46 AM
> > Hi Tim,
> >
> > UART Alpha Version
> > ************************
> > I have to demo Fuego to my management on one of our target board.
> > The target board has only UART Connectivity. I have two weeks to
> > setup target (along with cross compiler, config files etc.) and demo
> > the LTP test suite execution on it. LTP is already in the Pre-packed
> test list.
> > Should I be porting it again to my target to make it work?
> No.  What you do it add your toolchain to Fuego, and Fuego will build
> LTP for your target.  You can find instructions for adding a toolchain at:
> http://bird.org/fuego/Adding_a_toolchain
>
>
Thanks, I have already checked this link, will relook at it again with my
current objective.


> Can you say where you are getting your toolchain from, and what kind it is?
> (e.g. from Linaro, from your SoC vendor, from Debian packages, or building
> it yourself with
> crosstool or Yocto Project or Buildroot?)
>
>
gcc-linaro-aarch64-linux-gnu-4.8-2014.01_linux is the toolchain that I am
currently using
It is a debian package (buildroot).



> >How big an effort  will it be?
> If you were not using serial, it should be trivial.  However, one
> outstanding
> issue with the serial support is that it is not fast at transferring data.
> Our configuration of LTP requires transferring about 450mg of data, which
> takes too long over a serial port.  We have some sub-test configurations
> for LTP, that require less space.  I haven't measured them to see how much
> space they need on the target board.
>
> LTP can be refactored to have a smaller footprint, but this would require
> some work.
>
> In your case, I would be interested to hear how the device filesystem is
> populated
> now, and what size you have available for testing.  We might be able to
> customize
> a test spec to use a subset of LTP that would work for your device.
>
>
I want to use serial only for issuing command and getting status/logs.
The RFS is currently on an SD card where the cross compiled LTP has been
kept.
I would like to use the full LTP suite as well as LTP-DDT.



> > Also can I get the alpha version of UART so that I can use it for this
> demo?
>  Yes.  Everything needed for using the serial port as a transport option
> is included in my 'next' branch (and will be in the upcoming 1.1 release).
> I hope to release 1.1-rc1 today or Monday.  Serial support will be
> included in
> that release.
>
>
Thanks please give me the link whenever it is available and also any
instructions on how to update my current Fuego


> > Adding a new test suite
> > ***************************
> > 1. Is there any plan to add LTP-DDT test suite into Fuego container?
> There were no prior plans to do this, but it looks like an interesting
> suite to add.
> Since we have LTP, and LTP-DDT is a derivative, it should be relatively
> easy to
> add the individual tests from LTP.
>
> > 2. If I want to add my own test suite or test to Fuego dashboard, what
> is the
> > process?
> Please see this page:
> http://bird.org/fuego/Adding_a_test
>
>
Thanks I will check the above link. Can you also point me to the link
which helps me to run Fuego on port other than 8080?


> > 3. Is the dashboard customizable?
> Yes.  The Jenkins dashboard is extremely customizable, and there are
> numerous
> view options and plugins to configure how you want the dashboard to look.
> JTA and Fuego 1.0 used a lot of these plugins to create a specific look.
> Fuego 1.1 leaves this more as an exercise for the user, since each site
> may want
> their own Jenkins interface customizations.  We try to require a minimal
> set
> of Jenkins plugins for Fuego core functionality.  Then, individual users
> and sites
> can choose which of the Jenkins plugins to use for the dashboard look they
> want.
>
>
Thank is there any tips available already on customizing dashboard?

>
> > Please let me know.
>
> There would be some work involved to make existing LTP work over the serial
> port for your board.  But it should not be too difficult. More critical is
> how your
> distribution of Linux is configured to initialize.  Does your board come
> up to a login
> prompt, or directly into a shell prompt?
>

The board when booted will come up the buildroot login prompt and when
logged into will go into a shell prompt.
I hope I am clear with my requirements about LTP. Please let me know if you
have any further questions.

>
> Let me know the answers to my questions, and we can work from there.
>
> Regards,
>  -- Tim
>

[-- Attachment #2: Type: text/html, Size: 7984 bytes --]

Re: [Fuego] UART Alpha, Add New Test Suite to Fuego Dashboard

[dhinakar k]

[-- Attachment #1: Type: text/plain, Size: 5252 bytes --]

Hi Tim,

I figured out how to change Jenkins port (given below):

$ sudo docker exec -i -t id bash (container id to be provided)
$ vi /etc/default/Jenkins
Modify http port and restart container.

Regards,
Dhinakar

On Apr 3, 2017 12:51 PM, "dhinakar k" <dhinakar.k@gmail.com> wrote:

> Hi Tim,
>
> Thanks a lot for your detailed reply.
> Please find my comments inline.
>
> Regards,
> Dhinakar
>
> On Sat, Apr 1, 2017 at 11:52 AM, Bird, Timothy <Tim.Bird@sony.com> wrote:
>
>> See answers inline below.
>>
>> > -----Original Message-----
>> > From: dhinakar k on Friday, March 31, 2017 1:46 AM
>> > Hi Tim,
>> >
>> > UART Alpha Version
>> > ************************
>> > I have to demo Fuego to my management on one of our target board.
>> > The target board has only UART Connectivity. I have two weeks to
>> > setup target (along with cross compiler, config files etc.) and demo
>> > the LTP test suite execution on it. LTP is already in the Pre-packed
>> test list.
>> > Should I be porting it again to my target to make it work?
>> No.  What you do it add your toolchain to Fuego, and Fuego will build
>> LTP for your target.  You can find instructions for adding a toolchain at:
>> http://bird.org/fuego/Adding_a_toolchain
>>
>>
> Thanks, I have already checked this link, will relook at it again with my
> current objective.
>
>
>> Can you say where you are getting your toolchain from, and what kind it
>> is?
>> (e.g. from Linaro, from your SoC vendor, from Debian packages, or
>> building it yourself with
>> crosstool or Yocto Project or Buildroot?)
>>
>>
> gcc-linaro-aarch64-linux-gnu-4.8-2014.01_linux is the toolchain that I am
> currently using
> It is a debian package (buildroot).
>
>
>
>> >How big an effort  will it be?
>> If you were not using serial, it should be trivial.  However, one
>> outstanding
>> issue with the serial support is that it is not fast at transferring data.
>> Our configuration of LTP requires transferring about 450mg of data, which
>> takes too long over a serial port.  We have some sub-test configurations
>> for LTP, that require less space.  I haven't measured them to see how much
>> space they need on the target board.
>>
>> LTP can be refactored to have a smaller footprint, but this would require
>> some work.
>>
>> In your case, I would be interested to hear how the device filesystem is
>> populated
>> now, and what size you have available for testing.  We might be able to
>> customize
>> a test spec to use a subset of LTP that would work for your device.
>>
>>
> I want to use serial only for issuing command and getting status/logs.
> The RFS is currently on an SD card where the cross compiled LTP has been
> kept.
> I would like to use the full LTP suite as well as LTP-DDT.
>
>
>
>> > Also can I get the alpha version of UART so that I can use it for this
>> demo?
>>  Yes.  Everything needed for using the serial port as a transport option
>> is included in my 'next' branch (and will be in the upcoming 1.1 release).
>> I hope to release 1.1-rc1 today or Monday.  Serial support will be
>> included in
>> that release.
>>
>>
> Thanks please give me the link whenever it is available and also any
> instructions on how to update my current Fuego
>
>
>> > Adding a new test suite
>> > ***************************
>> > 1. Is there any plan to add LTP-DDT test suite into Fuego container?
>> There were no prior plans to do this, but it looks like an interesting
>> suite to add.
>> Since we have LTP, and LTP-DDT is a derivative, it should be relatively
>> easy to
>> add the individual tests from LTP.
>>
>> > 2. If I want to add my own test suite or test to Fuego dashboard, what
>> is the
>> > process?
>> Please see this page:
>> http://bird.org/fuego/Adding_a_test
>>
>>
> Thanks I will check the above link. Can you also point me to the link
> which helps me to run Fuego on port other than 8080?
>
>
>> > 3. Is the dashboard customizable?
>> Yes.  The Jenkins dashboard is extremely customizable, and there are
>> numerous
>> view options and plugins to configure how you want the dashboard to look.
>> JTA and Fuego 1.0 used a lot of these plugins to create a specific look.
>> Fuego 1.1 leaves this more as an exercise for the user, since each site
>> may want
>> their own Jenkins interface customizations.  We try to require a minimal
>> set
>> of Jenkins plugins for Fuego core functionality.  Then, individual users
>> and sites
>> can choose which of the Jenkins plugins to use for the dashboard look
>> they want.
>>
>>
> Thank is there any tips available already on customizing dashboard?
>
> >
>> > Please let me know.
>>
>> There would be some work involved to make existing LTP work over the
>> serial
>> port for your board.  But it should not be too difficult. More critical
>> is how your
>> distribution of Linux is configured to initialize.  Does your board come
>> up to a login
>> prompt, or directly into a shell prompt?
>>
>
> The board when booted will come up the buildroot login prompt and when
> logged into will go into a shell prompt.
> I hope I am clear with my requirements about LTP. Please let me know if
> you have any further questions.
>
>>
>> Let me know the answers to my questions, and we can work from there.
>>
>> Regards,
>>  -- Tim
>>
>
>

[-- Attachment #2: Type: text/html, Size: 8780 bytes --]