<div dir="ltr"><div>Hi Tim,</div><div><br></div><div>Yes you are right it is because of the leftover job configuration.</div><div>I cleared everything and recreated the jobs.</div><div>Now I see main.sh in the web interface and fuego_test.sh inside script folders.</div><div>Thanks for the response.</div><div><br></div><div>Regards,</div><div>Dhinakar</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 23, 2017 at 6:08 AM, Bird, Timothy <span dir="ltr"><<a href="mailto:Tim.Bird@sony.com" target="_blank">Tim.Bird@sony.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
<br>
> -----Original Message-----<br>
> From: dhinakar k [mailto:<a href="mailto:dhinakar.k@gmail.com">dhinakar.k@gmail.com</a>]<br>
><br>
> It seems the stream benchmark test is still expecting stream.sh file rather<br>
> than fuego_test.sh as per the v1.2 requirements.<br>
><br>
> It looks like a bug in the test. Please check.<br>
<br>
</span>I just did a clean install of fuego and fuego-core from my 'next' branches for<br>
each of these repositories on bitbucket. Then added a 'docker' node and the<br>
Benchmark.Stream test for that board.<br>
<br>
In the Execute Shell portion of the docker.default.Benchmark.<wbr>Stream job I see:<br>
export Reboot=false<br>
export Rebuild=true<br>
export Target_PreCleanup=true<br>
export Target_PostCleanup=true<br>
export TESTDIR=Benchmark.Stream<br>
export TESTSPEC=default<br>
export FUEGO_DEBUG=1<br>
timeout --signal=9 30m /bin/bash $FUEGO_CORE/engine/scripts/<wbr>main.sh<br>
<br>
The job executes main.sh, which executes $TESTDIR/fuego_test.sh<br>
<br>
So it looks OK in my configuration.<br>
<br>
You may have a leftover job configuration. Try removing the job and<br>
re-creating it with 'ftc add-jobs -b <your-board> -t Benchmark.Stream.<br>
Then look at the job configuration in the web interface, and let me know<br>
if you still see a problem.<br>
-- Tim<br>
</blockquote></div><br></div>