[Fuego] Fuego Digest, Vol 10, Issue 49
dhinakar k
dhinakar.k at gmail.com
Sat May 20 06:30:10 UTC 2017
Hi Tim,
Thanks very much for your detailed explanation about the different
mechanism adopted by Fuego to validate results.
The reference.log is something similar to the 'golden reference' that we
use during MFC encoding, decoding.
Standardizing the results across all tools is quite a challenge. I am happy
to see lot of thoughts going into it in Fuego.
Coming to the issue I am facing with git send-mail, I want to know if
something got messed up with my corporate and personal accounts.
I thought some corporate firewall might be blocking and hence tried to
configure gmail SMTP at home. But I see my corporate email details in the
error log or is it because the $ git commit -s done at office and home are
in queue waiting for moderator approval. Please confirm.
The below option suggested by you, looks good. I will explore that as we
also have to use bitbucket in one of your corporate project.
It's also very easy for me if you clone the repository on bitbucket, that I
can
pull patches from. But describing that Is outside the scope of this e-mail.
Regards,
Dhinakar
On Sat, May 20, 2017 at 1:49 AM, <fuego-request at lists.linuxfoundation.org>
wrote:
> Send Fuego mailing list submissions to
> fuego at lists.linuxfoundation.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.linuxfoundation.org/mailman/listinfo/fuego
> or, via email, send a message with subject or body 'help' to
> fuego-request at lists.linuxfoundation.org
>
> You can reach the person managing the list at
> fuego-owner at lists.linuxfoundation.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Fuego digest..."
>
>
> Today's Topics:
>
> 1. Re: HTTP ERROR 404 error when 'log' option is clicked for
> failed tests in fuego dashboard (Bird, Timothy)
> 2. Re: Fuego Digest, Vol 10, Issue 48 (dhinakar k)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 19 May 2017 16:26:02 +0000
> From: "Bird, Timothy" <Tim.Bird at sony.com>
> To: Daniel Sangorrin <daniel.sangorrin at toshiba.co.jp>,
> "dhinakar.k at samsung.com" <dhinakar.k at samsung.com>
> Cc: "fuego at lists.linuxfoundation.org"
> <fuego at lists.linuxfoundation.org>
> Subject: Re: [Fuego] HTTP ERROR 404 error when 'log' option is clicked
> for failed tests in fuego dashboard
> Message-ID:
> <ECADFF3FD767C149AD96A924E7EA6EAF1FA8935A at USCULXMSG01.am.sony.com>
> Content-Type: text/plain; charset="us-ascii"
>
>
>
> > -----Original Message-----
> > From: Daniel Sangorrin on Friday, May 19, 2017 12:40 AM
> >
> > > -----Original Message-----
> > > From: Dhinakar Kalyanasundaram on May 19, 2017 4:25 PM
> > Tim.Bird at sony.com
> > > Subject: RE: RE: RE: RE: RE: RE: RE: [Fuego] HTTP ERROR 404 error when
> 'log'
> > option is clicked for failed tests in fuego dashboard
> > >
> > > Hi Daniel,
> > >
> > >
> > >
> > > I have updated the reference.log file and the test is successful now.
> > >
> > > It was missing the following,
> > >
> > > [DaCapo.avrora|le]
> > > 1000000
> > >
> > > [DaCapo.xalan|le]
> > > 1000000
> > >
> >
> > Great, thanks for reporting back.
> >
> > >
> > >
> > > I have attached the reference.log file for your reference.
> > >
> > > I am not sure how to upload as patch, please let me know.
> >
> > $ git config --global user.name "Dhinakar Kalyanasundaram "
> > $ git config --global user.email "dhinakar.k at samsung.com"
> > $ git config --global sendemail.from "Dhinakar Kalyanasundaram
> > <dhinakar.k at samsung.com>"
> > $ git config --global sendemail.smtpserver mail.xxx.xxx.xx <-- put your
> server
> > $ git config --global sendemail.smtpserverport 25 <-- put your port
> >
> > $ git add engine/tests/Benchmark.Java/reference.log
> > $ git commit -s
> > java: fix the reference.log
> > write some explanation..
> > $ git send-email -1 --to fuego at lists.linuxfoundation.org
> >
>
> That's a handy summary. Thanks! Note that some exchange servers
> will mangle the patches (adjusting whitespace, folding lines, and/or
> converting the message body to base64). But it's worth trying it to
> see what happens. gmail servers are known to work, if your
> corporate firewalls will let you access the SMTP ports for that.
>
> It's also very easy for me if you clone the repository on bitbucket, that
> I can
> pull patches from. But describing that Is outside the scope of this
> e-mail.
>
> > > Thanks much, this exercise gave me an insight into the generic parsing
> > mechanism used by Fuego (parser.py, common.py,
> > > thresholds.awk etc.).
> > >
> > > One question, this 'reference.log' is auto generated by thresholds.awk
> so
> > the fix should be provided elsewhere otherwise it will
> > > overwrite the
> > >
> > > reference.log next time when it auto generates. Am I right?
> >
> > Currently we are not using thresholds.awk, but I think it is not
> automatic. You
> > have to call it from gawk
> > manually.
>
> That's correct. reference.log is not generated automatically. It is a
> judgement
> call when to save the reference log, to preserve results to compare
> against.
>
> You can ignore this for now, as Daniel says.
>
> Fuego has several different mechanisms for checking results:
> 1) a count of lines matching a string (this is what log_compare does)
> 2) a comparison of a list of numeric items parsed from a log with
> reference values (for benchmarks uses 'reference.log',
> this is what parser.py does)
> 3) the ability to check the test log for specific strings
> (this is what fail_check_cases does)
> 4) the ability to check the system logs for special string
> (this is to check for kernel Oopses. this is what syslog_cmp does)
> 5) a comparison of the parsed test log with another parsed log
> (testlog.[n|p].txt)
> (a text diff of processed text logs)
>
> We would like to add:
> 6) a comparison of results.json file with reference results
> (kind of like a json diff)
>
> The problem with 5 and 6 is that you really want to support the ability
> to ignore some parts of the diff that don't matter. I did some preliminary
> work on a smart diff program, but it needs more work.
>
> At some point, we plan to add some kind of 'save-reference'
> sub-command to ftc to save the reference material for 2), 5) and 6).
> Also we'd like to add a 'diff-results' sub-command, so end users
> can compare the results between runs, as well as between a run
> and the reference ('known-good') data.
> -- Tim
>
> P.S. I don't like the name 'reference.log' very much. It's not really a
> log.
> It should be named something like 'reference_values' or
> 'metric_thresholds'.
> And it should probably be in json format. But that's opening up a
> different
> discussion.
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 20 May 2017 01:48:52 +0530
> From: dhinakar k <dhinakar.k at gmail.com>
> To: fuego at lists.linuxfoundation.org, Daniel Sangorrin
> <daniel.sangorrin at toshiba.co.jp>, "Bird, Timothy" <
> Tim.Bird at sony.com>
> Subject: Re: [Fuego] Fuego Digest, Vol 10, Issue 48
> Message-ID:
> <CABehs3P5h8a7B6sDxVqshoxCTBO7zp575sw_BtAdaVFzef-g2g at mail.
> gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Daniel,
>
> I tried to upload the patch from my office using the steps that you
> provided.
> But it seems it is blocked in our office smtp server.
> And then I tried to upload from my home (gmail) getting the below error
> while trying to send email (last step).
>
> dhinakar at Ubuntu-RC510:~/fuego-core$ git send-email -1 --to
> fuego at lists.linuxfoundation.org
> /tmp/EipMH1mt3M/0001-java-fix-the-reference.log.patch
> (mbox) Adding cc: Dhinakar Kalyanasundaram <dhinakar.k at gmail.com> from
> line
> 'From: Dhinakar Kalyanasundaram <dhinakar.k at gmail.com>'
> (body) Adding cc: Dhinakar Kalyanasundaram <dhinakar.k at gmail.com> from
> line
> 'Signed-off-by: Dhinakar Kalyanasundaram <dhinakar.k at gmail.com>'
>
> From: Dhinakar Kalyanasundaram <dhinakar.k at samsung.com>
> To: fuego at lists.linuxfoundation.org
> Cc: Dhinakar Kalyanasundaram <dhinakar.k at gmail.com>
> Subject: [PATCH] java: fix the reference.log The below error is thrown
> because of missing threshold data in response.log file. 'AttributeError:
> 'NoneType' object has no attribute 'split' in signal_handler' The following
> were added to fix the issue. [DaCapo.avrora|le] 1000000 [DaCapo.xalan|le]
> 1000000
> Date: Sat, 20 May 2017 01:29:46 +0530
> Message-Id: <1495223986-12134-1-git-send-email-dhinakar.k at samsung.com>
> X-Mailer: git-send-email 2.7.4
>
> The Cc list above has been expanded by additional
> addresses found in the patch commit message. By default
> send-email prompts before sending whenever this occurs.
> This behavior is controlled by the sendemail.confirm
> configuration setting.
>
> For additional information, run 'git send-email --help'.
> To retain the current behavior, but squelch this message,
> run 'git config --global sendemail.confirm auto'.
>
> Send this email? ([y]es|[n]o|[q]uit|[a]ll): y
> 5.7.0 Must issue a STARTTLS command first. t13sm18602542pfa.126 - gsmtp
>
> I see my samsung.com id as well here, may be because the previous git
> update is waiting as well.
> Can you please help what to do in this case?
>
> Regards,
> Dhinakar
>
> On Fri, May 19, 2017 at 5:30 PM, <fuego-request at lists.linuxfoundation.org>
> wrote:
>
> > Send Fuego mailing list submissions to
> > fuego at lists.linuxfoundation.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > https://lists.linuxfoundation.org/mailman/listinfo/fuego
> > or, via email, send a message with subject or body 'help' to
> > fuego-request at lists.linuxfoundation.org
> >
> > You can reach the person managing the list at
> > fuego-owner at lists.linuxfoundation.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Fuego digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: HTTP ERROR 404 error when 'log' option is clicked for
> > failed tests in fuego dashboard (Daniel Sangorrin)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Fri, 19 May 2017 16:39:53 +0900
> > From: "Daniel Sangorrin" <daniel.sangorrin at toshiba.co.jp>
> > To: <dhinakar.k at samsung.com>
> > Cc: Tim.Bird at sony.com, fuego at lists.linuxfoundation.org
> > Subject: Re: [Fuego] HTTP ERROR 404 error when 'log' option is clicked
> > for failed tests in fuego dashboard
> > Message-ID: <006f01d2d073$1a96e9c0$4fc4bd40$@toshiba.co.jp>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Hi Dhinakar
> >
> > > -----Original Message-----
> > > From: Dhinakar Kalyanasundaram [mailto:dhinakar.k at samsung.com]
> > > Sent: Friday, May 19, 2017 4:25 PM
> > > To: Daniel Sangorrin
> > > Cc: Dhinakar Kalyanasundaram; fuego at lists.linuxfoundation.org;
> > Tim.Bird at sony.com
> > > Subject: RE: RE: RE: RE: RE: RE: RE: [Fuego] HTTP ERROR 404 error when
> > 'log' option is clicked for failed tests in fuego dashboard
> > >
> > > Hi Daniel,
> > >
> > >
> > >
> > > I have updated the reference.log file and the test is successful now.
> > >
> > > It was missing the following,
> > >
> > > [DaCapo.avrora|le]
> > > 1000000
> > >
> > > [DaCapo.xalan|le]
> > > 1000000
> > >
> >
> > Great, thanks for reporting back.
> >
> > >
> > >
> > > I have attached the reference.log file for your reference.
> > >
> > > I am not sure how to upload as patch, please let me know.
> >
> > $ git config --global user.name "Dhinakar Kalyanasundaram "
> > $ git config --global user.email "dhinakar.k at samsung.com"
> > $ git config --global sendemail.from "Dhinakar Kalyanasundaram <
> > dhinakar.k at samsung.com>"
> > $ git config --global sendemail.smtpserver mail.xxx.xxx.xx <-- put your
> > server
> > $ git config --global sendemail.smtpserverport 25 <-- put your port
> >
> > $ git add engine/tests/Benchmark.Java/reference.log
> > $ git commit -s
> > java: fix the reference.log
> > write some explanation..
> > $ git send-email -1 --to fuego at lists.linuxfoundation.org
> >
> > > Thanks much, this exercise gave me an insight into the generic parsing
> > mechanism used by Fuego (parser.py, common.py,
> > > thresholds.awk etc.).
> > >
> > > One question, this 'reference.log' is auto generated by thresholds.awk
> > so the fix should be provided elsewhere otherwise it will
> > > overwrite the
> > >
> > > reference.log next time when it auto generates. Am I right?
> >
> > Currently we are not using thresholds.awk, but I think it is not
> > automatic. You have to call wit from gawk
> > manually. Probably it doesn't work at the moment because the plot.data
> > format has changed. I think I will
> > add some similar mechanism in the future, but for now just don't worry
> > about it.
> >
> > Thanks,
> > Daniel
> >
> >
> > >
> > >
> > >
> > > Regards,
> > >
> > > Dhinakar,
> > >
> > > Senior Technical Manager,
> > >
> > > 2-07-526, Phoenix Building,
> > >
> > > +91-9902007650
> > >
> > > Samsung Research Institute, Bangalore.
> > >
> > >
> > >
> > >
> > >
> > > --------- Original Message ---------
> > >
> > > Sender : Dhinakar Kalyanasundaram <dhinakar.k at samsung.com> Senior
> > Technical Manager/SSIR-FDS SW/Samsung Electronics
> > >
> > > Date : 2017-05-19 10:13 (GMT+5:30)
> > >
> > > Title : RE: RE: RE: RE: RE: RE: [Fuego] HTTP ERROR 404 error when 'log'
> > option is clicked for failed tests in fuego dashboard
> > >
> > > To : null<daniel.sangorrin at toshiba.co.jp>
> > >
> > > CC : Dhinakar Kalyanasundaram<dhinakar.k at samsung.com>,
> null<fuego at lists.
> > linuxfoundation.org>
> > >
> > >
> > >
> > > Sure Daniel,
> > >
> > > I will add the required thresholds to the reference.log and check if it
> > works.
> > >
> > > Will let you know by today.
> > >
> > >
> > >
> > > Regards,
> > >
> > > Dhinakar,
> > >
> > > Senior Technical Manager,
> > >
> > > 2-07-526, Phoenix Building,
> > >
> > > +91-9902007650
> > >
> > > Samsung Research Institute, Bangalore.
> > >
> > >
> > >
> > >
> > >
> > > --------- Original Message ---------
> > >
> > > Sender : Daniel Sangorrin <daniel.sangorrin at toshiba.co.jp>
> > >
> > > Date : 2017-05-19 05:41 (GMT+5:30)
> > >
> > > Title : RE: RE: RE: RE: RE: [Fuego] HTTP ERROR 404 error when 'log'
> > option is clicked for failed tests in fuego dashboard
> > >
> > > To : Dhinakar Kalyanasundaram<dhinakar.k at samsung.com>,
> > fuego at lists.linuxfoundation.org
> > >
> > >
> > >
> > > Hi Dhinakar,
> > >
> > > > Traceback (most recent call last):
> > > > File "/fuego-core/engine/tests/Benchmark.Java/parser.py", line 42,
> > in <module>
> > > > sys.exit(plib.process_data(ref_section_pat, cur_dict, 'm', 'FPS,
> > %'))
> > > > File "/fuego-core/engine/scripts/parser/common.py", line 92, in
> > process_data
> > > > rc = compare(thresholds, test_results, criteria)
> > > > File "/fuego-core/engine/scripts/parser/common.py", line 422, in
> > compare
> > > > thresholds_split = thresholds.get(key).split()
> > > > AttributeError: 'NoneType' object has no attribute 'split'
> > > > in signal_handler
> > > > ##### doing fuego phase: post_test ########
> > > > Warning: Permanently added '107.108.83.19' (ECDSA) to the list of
> > known hosts.
> > > > Warning: Permanently added '107.108.83.19' (ECDSA) to the list of
> > known hosts.
> > > > Warning: Permanently added '107.108.83.19' (ECDSA) to the list of
> > known hosts.
> > > > Warning: Permanently added '107.108.83.19' (ECDSA) to the list of
> > known hosts.
> > > > Warning: Permanently added '107.108.83.19' (ECDSA) to the list of
> > known hosts.
> > > > Build step 'Execute shell' marked build as failure
> > > > [description-setter] Description set: <a href="/fuego/userContent/
> > fuego.logs/Benchmark.Java/ubuntu-x86-
> > > > target.default.1.1/testlog.txt">log</a>
> > > > Finished: FAILURE
> > > >
> > >
> > > This looks like the bug I solved with the patch I sent yesterday. The
> > reason is that
> > > the reference.log file was not including all of the thresholds. Because
> > of that some
> > > keys were not available in the dictionary used inside the parser.
> > >
> > > Could you add the same thresholds to the reference.log and see if it
> > works?
> > >
> > > --- a/engine/tests/Benchmark.Java/reference.log
> > > +++ b/engine/tests/Benchmark.Java/reference.log
> > > @@ -6,6 +6,10 @@
> > > 1000000
> > > [DaCapo.lusearch|le]
> > > 1000000
> > > +[DaCapo.avrora|le]
> > > +1000000
> > > +[DaCapo.xalan|le]
> > > +1000000
> > > [SciMark.Composite_Score|ge]
> > > 0
> > > [SciMark.FFT|ge]
> > >
> > > If that works that could be your first patch for fuego! ;)
> > >
> > > Thanks,
> > > Daniel
> > >
> > >
> > >
> > >
> > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Dhinakar,
> > > >
> > > > Senior Technical Manager,
> > > >
> > > > 2-07-526, Phoenix Building,
> > > >
> > > > +91-9902007650
> > > >
> > > > Samsung Research Institute, Bangalore.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --------- Original Message ---------
> > > >
> > > > Sender : Dhinakar Kalyanasundaram <dhinakar.k at samsung.com> Senior
> > Technical Manager/SSIR-FDS SW/Samsung Electronics
> > > >
> > > > Date : 2017-05-18 20:44 (GMT+5:30)
> > > >
> > > > Title : RE: RE: RE: RE: [Fuego] HTTP ERROR 404 error when 'log'
> option
> > is clicked for failed tests in fuego dashboard
> > > >
> > > > To : null<daniel.sangorrin at toshiba.co.jp>, Dhinakar Kalyanasundaram<
> > dhinakar.k at samsung.com>,
> > > > null<fuego at lists.linuxfoundation.org>
> > > >
> > > >
> > > >
> > > > Hi Daniel.
> > > >
> > > >
> > > >
> > > > Thanks for your patch.
> > > >
> > > > I got past that Benchmark.java error now.
> > > >
> > > > But I see the following error in the log because of which the test is
> > failing.
> > > >
> > > > ===== DaCapo 9.12 avrora PASSED in 2214 msec =====
> > > > OpenJDK 64-Bit Server VM warning: You have loaded library
> > /tmp/jna8507861728258266844.tmp which might have disabled stack
> > > > guard. The VM will try to fix the stack guard now.
> > > > It's highly recommended that you fix the library with 'execstack -c
> > <libfile>', or link it with '-z noexecstack'.
> > > >
> > > >
> > > >
> > > > Though it is not in fuego scope, I just wanted to ask you if you have
> > any clue about fixing the above error because I do not fine
> > > > jna8507861728258266844.tmp under /tmp directory.
> > > >
> > > >
> > > >
> > > > @Daniel / Tim
> > > >
> > > >
> > > >
> > > > Also, whenever I do a git pull and update fuego or fuego-core do I
> > need to remove and recreate the docker container?
> > > >
> > > > Because it will clear every test and results, boards etc. from
> > Jenkins. I will loose the test history and also custom/internal tests
> > > > integrated into fuego.
> > > >
> > > > What is the general procedure to upgrade fuego? Is there any link
> > which I can refer to? Please let me know.
> > > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > > Dhinakar,
> > > >
> > > > Senior Technical Manager,
> > > >
> > > > 2-07-526, Phoenix Building,
> > > >
> > > > +91-9902007650
> > > >
> > > > Samsung Research Institute, Bangalore.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --------- Original Message ---------
> > > >
> > > > Sender : Daniel Sangorrin <daniel.sangorrin at toshiba.co.jp>
> > > >
> > > > Date : 2017-05-18 11:54 (GMT+5:30)
> > > >
> > > > Title : RE: RE: RE: [Fuego] HTTP ERROR 404 error when 'log' option is
> > clicked for failed tests in fuego dashboard
> > > >
> > > > To : Dhinakar Kalyanasundaram<dhinakar.k at samsung.com>,
> > fuego at lists.linuxfoundation.org
> > > >
> > > >
> > > >
> > > > Hi Dhinakar,
> > > >
> > > > > -----Original Message-----
> > > > > From: Dhinakar Kalyanasundaram [mailto:dhinakar.k at samsung.com]
> > > > > Sent: Thursday, May 18, 2017 11:36 AM
> > > > > To: Daniel Sangorrin; Dhinakar Kalyanasundaram;
> > fuego at lists.linuxfoundation.org
> > > > > Subject: RE: RE: RE: [Fuego] HTTP ERROR 404 error when 'log' option
> > is clicked for failed tests in fuego dashboard
> > > > >
> > > > > Hi Daniel,
> > > > >
> > > > >
> > > > >
> > > > > > Then you must be running an outdated version of fuego-core in
> which
> > > > > > the spec was using "testName" : "Benchmark.java" instead of
> > "Benchmark.Java".
> > > > >
> > > > >
> > > > > Yeah you are right, I will update and retest. Thanks.
> > > > >
> > > >
> > > > Please check the patch that I sent. It's on my next branch as well.
> > > > Probably the problem is similar.
> > > >
> > > > Thanks,
> > > > Daniel
> > > >
> > > >
> > > > >
> > > > >
> > > > > Regards,
> > > > >
> > > > > Dhinakar,
> > > > >
> > > > > Senior Technical Manager,
> > > > >
> > > > > 2-07-526, Phoenix Building,
> > > > >
> > > > > +91-9902007650
> > > > >
> > > > > Samsung Research Institute, Bangalore.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --------- Original Message ---------
> > > > >
> > > > > Sender : Daniel Sangorrin <daniel.sangorrin at toshiba.co.jp>
> > > > >
> > > > > Date : 2017-05-18 08:01 (GMT+5:30)
> > > > >
> > > > > Title : RE: RE: [Fuego] HTTP ERROR 404 error when 'log' option is
> > clicked for failed tests in fuego dashboard
> > > > >
> > > > > To : Dhinakar Kalyanasundaram<dhinakar.k at samsung.com>,
> > fuego at lists.linuxfoundation.org
> > > > >
> > > > >
> > > > >
> > > > > Hi Dhinakar,
> > > > >
> > > > > > It actually exists but I still get that error.
> > > > >
> > > > > Then you must be running an outdated version of fuego-core in which
> > > > > the spec was using "testName" : "Benchmark.java" instead of
> > "Benchmark.Java".
> > > > >
> > > > > Please can you upate fuego-core to the latest version?
> > > > >
> > > > > If you can't then please check that the spec file, the folder name
> > and the file
> > > > > have the same spelling (i.e.: Java instead of java).
> > > > >
> > > > > [Note] in the next branch we require all tests to be named
> > fuego_test.sh to
> > > > > reduce this kind of spelling mistakes.
> > > > >
> > > > > Thanks,
> > > > > Daniel
> > > > >
> > > > >
> > > > > > But other tests such as bonnie, cyclictest, dbench, Dhrystone,
> > ebizzy etc. have passed.
> > > > > >
> > > > > > Please check my console log below.
> > > > > >
> > > > > > Any environment or path issue?
> > > > > >
> > > > > >
> > > > > >
> > > > > > Started by user anonymous <http://107.108.83.19:8080/
> > fuego/user/null>
> > > > > > Building remotely on ubuntu-x86-target <
> http://107.108.83.19:8080/
> > fuego/computer/ubuntu-x86-target> in workspace /fuego-
> > > > > > rw/buildzone
> > > > > > [buildzone] $ /bin/sh -xe /tmp/hudson4082135732911905617.sh
> > > > > > + export Reboot=false
> > > > > > + Reboot=false
> > > > > > + export Rebuild=true
> > > > > > + Rebuild=true
> > > > > > + export Target_PreCleanup=true
> > > > > > + Target_PreCleanup=true
> > > > > > + export Target_PostCleanup=true
> > > > > > + Target_PostCleanup=true
> > > > > > + export TESTDIR=Benchmark.java
> > > > > > + TESTDIR=Benchmark.java
> > > > > > + export TESTNAME=java
> > > > > > + TESTNAME=java
> > > > > > + export TESTSPEC=default
> > > > > > + TESTSPEC=default
> > > > > > + timeout --signal=9 100m /bin/bash /fuego-core/engine/tests/
> > Benchmark.java/java.sh
> > > > > > /bin/bash: /fuego-core/engine/tests/Benchmark.java/java.sh: No
> > such file or directory
> > > > > > Build step 'Execute shell' marked build as failure
> > > > > > [description-setter] Description set: <a
> href="/fuego/userContent/
> > fuego.logs/Benchmark.java/ubuntu-x86-
> > > > > > target.default.2.2/testlog.txt">log</a>
> > > > > > Finished: FAILURE
> > > > > >
> > > > > >
> > > > > >
> > > > > > Regards,
> > > > > >
> > > > > > Dhinakar,
> > > > > >
> > > > > > Senior Technical Manager,
> > > > > >
> > > > > > 2-07-526, Phoenix Building,
> > > > > >
> > > > > > +91-9902007650
> > > > > >
> > > > > > Samsung Research Institute, Bangalore.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --------- Original Message ---------
> > > > > >
> > > > > > Sender : Daniel Sangorrin <daniel.sangorrin at toshiba.co.jp>
> > > > > >
> > > > > > Date : 2017-05-18 05:32 (GMT+5:30)
> > > > > >
> > > > > > Title : RE: [Fuego] HTTP ERROR 404 error when 'log' option is
> > clicked for failed tests in fuego dashboard
> > > > > >
> > > > > > To : Dhinakar Kalyanasundaram<dhinakar.k at samsung.com>,
> > fuego at lists.linuxfoundation.org
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hi Dhinakar,
> > > > > >
> > > > > > > But I think in case of failure the 'testlog.txt' can be created
> > and populated with the error reason displayed in 'Console Output'.
> > > > > > >
> > > > > > > In this case it is, /bin/bash: /fuego-core/engine/tests/
> Benchmark.java/java.sh:
> > No such file or directory
> > > > > >
> > > > > > Are you sure?
> > > > > > /fuego-core/engine/tests/Benchmark.java does not exist in Fuego.
> > > > > > /fuego-core/engine/tests/Benchmark.Java does.
> > > > > >
> > > > > > Also please make sure that /fuego-core/engine/tests/
> Benchmark.Java/Java.sh
> > exists as in here:
> > > > > > https://bitbucket.org/tbird20d/fuego-
> > > > > > core/src/d449a0a8ed0e1851c29c5895fee0162da59777de/engine/tests/
> > Benchmark.Java/?at=master
> > > > > >
> > > > > > Thanks,
> > > > > > Daniel
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Regards,
> > > > > > >
> > > > > > > Dhinakar,
> > > > > > >
> > > > > > > Senior Technical Manager,
> > > > > > >
> > > > > > > 2-07-526, Phoenix Building,
> > > > > > >
> > > > > > > +91-9902007650
> > > > > > >
> > > > > > > Samsung Research Institute, Bangalore.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > <http://ext.samsung.net/mail/ext/v1/external/status/update?
> > userid=dhinakar.k&do=bWFpbElEPTIwMTcwNTE3MTE0MzU1ZXBjbXM
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > 1cDVjOTRkMDZmOTY3ZDBlMWVkYWQ1MDBkNGUyNjdjNjBiNiZyZWNpcGllbnR
> > BZGRyZXNzPWZ1ZWdvQGxpc3RzLmxpbnV4Zm91bmR
> > > > > > > hdGlvbi5vcmc_>
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > > <http://ext.samsung.net/mail/ext/v1/external/status/update?
> > userid=dhinakar.k&do=bWFpbElEPTIwMTcwNTE4MDIwMjAxZXBjbXM
> > > > > >
> > > > >
> > > >
> > > 1cDcxNDExMjViOTIwYmMyNGExOGZmYzE3NzhiMjdhOTk1MCZyZWNpcGllbnR
> > BZGRyZXNzPWRhbmllbC5zYW5nb3JyaW5AdG9zaGliYS5
> > > > > > jby5qcA__>
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > <http://ext.samsung.net/mail/ext/v1/external/status/update?
> > userid=dhinakar.k&do=bWFpbElEPTIwMTcwNTE4MDIzNTQ4ZXBjbXM
> > > > >
> > > >
> > > 1cDQxMjkyYjgyNDRmODg1ZmFmYTVjMjk5MzI4MTc3Mjc2MiZyZWNpcGllbnR
> > BZGRyZXNzPWRhbmllbC5zYW5nb3JyaW5AdG9zaGliYS5j
> > > > > by5qcA__>
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > <http://ext.samsung.net/mail/ext/v1/external/status/update?
> > userid=dhinakar.k&do=bWFpbElEPTIwMTcwNTE4MTUzNDI1ZXBjbXM
> > > >
> > > 1cDY0ZmNlZGY3ODkzZGY2NTBkYTY1ZDc3MmQ2MTUyMTNhMSZyZWNpcGllbnR
> > BZGRyZXNzPWRhbmllbC5zYW5nb3JyaW5AdG9zaGliYS
> > > > 5jby5qcA__>
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > <http://ext.samsung.net/mail/ext/v1/external/status/update?
> > userid=dhinakar.k&do=bWFpbElEPTIwMTcwNTE5MDcyNTE2ZXBjbXM
> > > 1cDFmMzY4NDI4OWZmOWVmMDUzNmVkY2E3Yzg3MDY3MWM4YyZyZWNpcGllbnR
> > BZGRyZXNzPWRhbmllbC5zYW5nb3JyaW5AdG9za
> > > GliYS5jby5qcA__>
> >
> >
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > Fuego mailing list
> > Fuego at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/fuego
> >
> >
> > End of Fuego Digest, Vol 10, Issue 48
> > *************************************
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.linuxfoundation.org/pipermail/fuego/
> attachments/20170520/406a8982/attachment.html>
>
> ------------------------------
>
> _______________________________________________
> Fuego mailing list
> Fuego at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/fuego
>
>
> End of Fuego Digest, Vol 10, Issue 49
> *************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20170520/461eed17/attachment-0001.html>
More information about the Fuego
mailing list