From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hms365.onmicrosoft.com; s=selector1-hms-se; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=P21R/qUx5/pt5QYfQUqcJevfVJxMB0NLdvxTG4ePUaY=; b=LusZZ25qqZDdrNzA3vmKuDadtEqHtOs4O559qMgExXxccFZcBNjz+NeI4+jESsoGCQmJOyeklVih8nNmoanauZ1Ni31eRpFcd65FB06vfqiN6BwP0JFCepXVyjNDRUcqNJ7w0H3aj7IIW3nN4O1PNjALktW0gogt7cGSrTsNTGY= From: Rafael Gago Castano Date: Tue, 16 May 2017 14:38:01 +0000 Message-ID: References: , , , , , In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [Fuego] First steps with fuego List-Id: Mailing list for the Fuego test framework List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Bird, Timothy" Cc: "fuego@lists.linuxfoundation.org" > Add a stub function to fuego-core/engine/overlays/base/base-board.fuegocl= ass, > like so: > function ov_board_setup() { > =A0=A0=A0=A0=A0=A0=A0 return > } > By convention, functions in the base class start with "ov_" > which is short for "overlay".=A0 I'm not sure that's required, but > it won't hurt for now. >=20 > Now, define an override function in your board file, like so: >=20 > override-func ov_board_setup() { > =A0=A0=A0=A0=A0=A0=A0 echo "do your setup operations here" > } > TARGET_SETUP_LINK=3D"ov_board_setup" >=20 > This would go in fuego/fuego-ro/boards/.board >=20 > Please let me know if this works for you.=A0 It does. Thanks, now that you posted it I remember about reading something = about override-func on the manual. I ended up implementing a board setup/teardown function that is only enable= d by a variable set by a setup/teardown test. So now I have a setup test, s= erial rx and teardown test that are working and integrated with our environ= ment. That it's an achievement considering the little amount of time that I= have spent. Then I added the setup and teardown tests as the first and the last ones of= a test plan, but it looks like Jenkins doesn't respect the testplans .json= file order on the .batch generated file, it looks like if they are sorted = alphabetically.=20 How are test runs meant to be scheduled/triggered on jenkins without user i= ntervention? I tried ftc put-request but it doesn't return a request id. PS: I sent another variant of the RX serial test to the mailing list. That = one is more compact and doesn't require any modification to Fuego. Previous= ly I was trying to synchronize through "primitives" (I still was thinking a= s if I was using LAVA); Fuego has implicit host-dut synchronization. =