[Fuego] Fuego v1.1 release
Daniel Sangorrin
daniel.sangorrin at toshiba.co.jp
Thu Apr 6 04:33:35 UTC 2017
Hi Dhinakar,
> Cloning into '/ttc'...
> fatal: unable to access 'https://guthib.com/tbird20d/ttc.git/': Could not resolve host: github.com <http://github.com>
> The command '/bin/sh -c git clone https://github.com/tbird20d/ttc.git $INST_FUEGO_ENGINE_PATH/ttc' returned a non-zero code:
> 128
>
> I tried 'export GIT_SSL_NO_VERIFY=1' and also 'git config http.sslVerify "false"' but no use. What else to do?
Are you working behind a proxy?
If that's the case, could you add this line right before the "RUN git clone ..." line and try again?
RUN if [ -n "$HTTP_PROXY" ]; then git config --global http.proxy ${HTTP_PROXY}; fi
Thanks,
Daniel
> On Apr 5, 2017 6:20 PM, "dhinakar k" <dhinakar.k at gmail.com <mailto:dhinakar.k at gmail.com> > wrote:
>
>
> Hi Tim,
>
> Thank you very much for your prompt response.
> I will try as per your advise and get back to you with my results.
>
> Regards,
> Dhinakar
>
> On Apr 5, 2017 10:28 AM, "Bird, Timothy" <Tim.Bird at sony.com <mailto:Tim.Bird at sony.com> > wrote:
>
>
> Yeah - my hosting service had scheduled maintenance today that I forgot about.
> But it seems to be up again now. Sorry about that.
>
> Please try again. Also, if you've already cloned the fuego-core repository, please
> do a 'git pull' in that repository to get the latest stuff. I just found some issues
> with the serial transport, with my toolchain. Also, be advised that you need
> to make sure that your user account has access to the serial port. When the
> docker container is created, it uses your user account and maps that to the
> user 'jenkins' inside the container. This is the user that is in effect when tests
> are run (and hence when the serial port is accessed during a test).
>
> Bottom line: if you can access the serial port as your regular user account, then
> Fuego should be able to access it from inside the docker container as the 'jenkins'
> user, which is required for the tests to work.
>
> Have fun!
> -- Tim
>
>
> > -----Original Message-----
> > From: dhinakar k [mailto:dhinakar.k at gmail.com <mailto:dhinakar.k at gmail.com> ]
> > Sent: Tuesday, April 04, 2017 9:31 PM
> > To: Bird, Timothy <Tim.Bird at sony.com <mailto:Tim.Bird at sony.com> >
> > Cc: fuego at lists.linuxfoundation.org <mailto:fuego at lists.linuxfoundation.org>
> > Subject: RE: Fuego v1.1 release
> >
> > Hi Tim,
> >
> > Thank you very much. I will try as per your instructions and get back in case of
> > issues.
> > But at present I'm not able to access this link
> > http://bird.org/fuego/Quickstart_Guide <http://bird.org/fuego/Quickstart_Guide>
> > <http://bird.org/fuego/Quickstart_Guide <http://bird.org/fuego/Quickstart_Guide> > Can you please check?
> >
> > Regards,
> > Dhinakar
> >
> > On Apr 5, 2017 9:36 AM, "Bird, Timothy" <Tim.Bird at sony.com <mailto:Tim.Bird at sony.com>
> > <mailto:Tim.Bird at sony.com <mailto:Tim.Bird at sony.com> > > wrote:
> >
> >
> > Fuego release 1.1, release candidate 2, is available now in my master
> > branch on bitbucket.
> >
> > Please follow the instructions on this page to download and use this
> > version of Fuego:
> > http://bird.org/fuego/Quickstart_Guide <http://bird.org/fuego/Quickstart_Guide>
> > <http://bird.org/fuego/Quickstart_Guide <http://bird.org/fuego/Quickstart_Guide> > .
> >
> > Please note that for serial port usage, you need to build the docker
> > container with access
> > to the serial port on the host. So you should use the command:
> > docker-create-usb-privileged-container.sh (instead of docker-create-
> > container.sh).
> > You may need to edit this script to add support for the particular
> > device node on your
> > host system that represents the serial port connected to your target
> > board. If is
> > a USB serial, or ACM0 or ACM1, the existing script should work.
> >
> > Once the docker container is running, and the board is configured,
> > manually access the
> > serial port on your board, and login, if needed, and make sure
> > the serial port connection is sitting at a shell prompt. Then,
> > disconnect any terminal or
> > serial programs connected to that port. Fuego must have sole access
> > to the serial line
> > in order to function properly.
> >
> > In your case, I would first try running a test that is very small, and
> > involves no compilation,
> > just to test the serial port operation.
> >
> > One test you can try is: Functional.fuego_board_check. You can
> > make a job for this with:
> > $ ftc add-job -b <your_board_name> -t
> > Functional.fuego_board_check -s default
> >
> > For a first run, to get more logging information, edit the job
> > configuration, and uncomment
> > the line that has this:
> > #FUEGO_DEBUG=1
> >
> > That is, remove the leading hash, and Fuego will add extra debug
> > information to the console output
> > for the test, which you can view in the Jenkins interface.
> >
> > Save that change to the job configuration.
> >
> > Then, "build" that job in the Jenkins interface.
> >
> > Proceed to this point, and let me know if anything fails. Then we can
> > discuss ideas for how to get
> > the LTP code onto the target board, and how to alter the existing test
> > to use the pre-installed
> > LTP software.
> >
> > Good luck.
> > -- Tim
> >
> > P.S. Documents on the wiki are currently in flux, to reflect
> > information for the 1.1 release. They should
> > be ready in time for the actual release. But please be patient as
> > information may change in the next
> > few days.
> >
> >
> > > -----Original Message-----
> > > From: dhinakar k [mailto:dhinakar.k at gmail.com <mailto:dhinakar.k at gmail.com>
> > <mailto:dhinakar.k at gmail.com <mailto:dhinakar.k at gmail.com> > ]
> > > Sent: Tuesday, April 04, 2017 7:58 PM
> > > To: Bird, Timothy <Tim.Bird at sony.com <mailto:Tim.Bird at sony.com>
> > <mailto:Tim.Bird at sony.com <mailto:Tim.Bird at sony.com> > >
> > > Cc: fuego at lists.linuxfoundation.org <mailto:fuego at lists.linuxfoundation.org>
> > <mailto:fuego at lists.linuxfoundation.org <mailto:fuego at lists.linuxfoundation.org> >
> > > Subject: Fuego v1.1 release
> > >
> > > Hi,
> > >
> > > May I know when will Fuego v1.1, which has support for serial
> > connectivity to
> > > target boards be released?
> > >
> > > Regards,
> > > Dhinakar
> > >
> > > On Apr 3, 2017 3:26 PM, "dhinakar k" <dhinakar.k at gmail.com <mailto:dhinakar.k at gmail.com>
> > <mailto:dhinakar.k at gmail.com <mailto:dhinakar.k at gmail.com> >
> >
> > > <mailto:dhinakar.k at gmail.com <mailto:dhinakar.k at gmail.com> <mailto:dhinakar.k at gmail.com
> <mailto:dhinakar.k at gmail.com> > > >
> > wrote:
> > >
> > >
> > > 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 at gmail.com <mailto:dhinakar.k at gmail.com>
> > <mailto:dhinakar.k at gmail.com <mailto:dhinakar.k at gmail.com> >
> >
> > > <mailto:dhinakar.k at gmail.com <mailto:dhinakar.k at gmail.com> <mailto:dhinakar.k at gmail.com
> <mailto:dhinakar.k at 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 at sony.com <mailto:Tim.Bird at sony.com> <mailto:Tim.Bird at sony.com <mailto:Tim.Bird at sony.com>
> >
> > <mailto:Tim.Bird at sony.com <mailto:Tim.Bird at sony.com> <mailto:Tim.Bird at sony.com
> <mailto:Tim.Bird at 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 <http://bird.org/fuego/Adding_a_toolchain>
> > <http://bird.org/fuego/Adding_a_toolchain <http://bird.org/fuego/Adding_a_toolchain> >
> > > <http://bird.org/fuego/Adding_a_toolchain <http://bird.org/fuego/Adding_a_toolchain>
> > <http://bird.org/fuego/Adding_a_toolchain <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 <http://bird.org/fuego/Adding_a_test>
> > <http://bird.org/fuego/Adding_a_test <http://bird.org/fuego/Adding_a_test> >
> > > <http://bird.org/fuego/Adding_a_test <http://bird.org/fuego/Adding_a_test>
> > <http://bird.org/fuego/Adding_a_test <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
> > >
> > >
> > >
> >
> >
> >
> >
>
>
More information about the Fuego
mailing list