All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rafael Gago Castano <RGC@hms.se>
To: "fuego@lists.linuxfoundation.org" <fuego@lists.linuxfoundation.org>
Subject: [Fuego] First steps with fuego
Date: Tue, 9 May 2017 09:49:20 +0000	[thread overview]
Message-ID: <HE1PR06MB30367AFE3FC1DEECE3B13713C2EF0@HE1PR06MB3036.eurprd06.prod.outlook.com> (raw)

Hello,

We are a group that is using a LAVA setup, but we are not completely happy with it and we are trying alternatives. We like from fuego that it seems to be more hackable, it runs the server from a container (hopefully being able to develop tests locally) and doesn't try to bring in a lot of Web technologies/languages. 

So far I have some questions.

I have built the .pdf under fuego/docs (fuego-docs.pdg) and I'm trying to follow it on Ubuntu 16.04. I'm now blocked at step 4. The jenkins Web interface  is not showing anything specific to fuego, I see just a vanilla Jenkins server with no tabs, not something like this:

http://bird.org/fuego-files/fuego-dashboard-history.png

I was able to submit some tests (Initial test section on the README file) by using the ftc tool and I saw some of them failing (docker.default.Functional.LTP,  docker.default.Functional.glib), but the Jenkins interface doesn't let me do anything. I'm not very well versed on Jenkins and Docker setups so I might be doing something wrong. What should I check?

Then I saw no reference about what in LAVA is called multinode tests (just for someone reading this that doesn't know LAVA: a test using more than one board involved to be able to test e.g. communication hardware). If this is achievable with Fuego, how would be do?

BR,
Rafa.


             reply	other threads:[~2017-05-09  9:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09  9:49 Rafael Gago Castano [this message]
2017-05-09 19:04 ` [Fuego] First steps with fuego Bird, Timothy
2017-05-10  6:32   ` Rafael Gago Castano
2017-05-10 13:12   ` Rafael Gago Castano
2017-05-10 19:30     ` Bird, Timothy
     [not found]       ` <HE1PR06MB3036959D51FD5FBFC02208C8C2ED0@HE1PR06MB3036.eurprd06.prod.outlook.com>
     [not found]         ` <ECADFF3FD767C149AD96A924E7EA6EAF1FA88A98@USCULXMSG01.am.sony.com>
2017-05-12  9:38           ` Rafael Gago Castano
2017-05-12 18:05             ` Bird, Timothy
2017-05-15  8:21               ` Rafael Gago Castano
2017-05-12 14:33         ` Rafael Gago Castano
2017-05-12 18:39           ` Bird, Timothy
2017-05-15 13:57             ` Rafael Gago Castano
2017-05-15 22:37               ` Bird, Timothy
2017-05-16 14:38                 ` Rafael Gago Castano
2017-05-17  5:06                   ` Bird, Timothy
2017-05-17  6:35                     ` Rafael Gago Castano
2017-05-17 15:33                       ` Bird, Timothy
2017-05-22  8:23                         ` Rafael Gago Castano
2017-05-22 20:51                           ` Bird, Timothy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=HE1PR06MB30367AFE3FC1DEECE3B13713C2EF0@HE1PR06MB3036.eurprd06.prod.outlook.com \
    --to=rgc@hms.se \
    --cc=fuego@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.