Re: maintaining sumo (was Re: [PATCH][thud] cve-check: backport rewrite from master)

[<Mikko.Rapeli@bmw.de>]

Hi,

On Thu, Nov 07, 2019 at 10:41:42AM +0000, Ryan Harkin wrote:
<snip>
> Not sure if it helps, but I have a Jenkins job that tests sumo on a trigger
> (there is one for Warrior also):
> 
> https://ci.linaro.org/job/warp7-openembedded-sumo/
> 
> eg. it was triggered when Armin's patch was merged yesterday.
> 
> This builds Sumo, based on Linaro's OE-RPB distro for NXP WaRP7
> (imx7s-warp). It then runs the build in our LAVA lab (although the boards
> have gone down recently, they're normally up). Once the boards are up
> again, I'll add ptest to the job, to give it a more thorough workout. I'll
> also add the sumo-next branch to the list of build configurations.

Could it make sense to also test sumo-next using this job? Also, I would not mind
seeing test trigger and result emails on this list as long as access to logs and details
is open to everyone.

I checked the jenkins build job config and looks quite straight forward. Did not see
the actual target testing logs though.

Cheers,

-Mikko