Skip to contentSkip to conversation

Fuego Digest, Vol 10, Issue 49

Fuego dhinakar k 2 participants 3 messages May 20, 2017 – May 22, 2017 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

dhinakar k

author
#1 lore raw

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

Quoted 877 lines · On Sat, May 20, 2017 at 1:49 AM, <[email protected]>…

Send Fuego mailing list submissions to
[email protected]

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
[email protected]

You can reach the person managing the list at
[email protected]

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" <[email protected]>
To: Daniel Sangorrin <[email protected]>,
"[email protected]" <[email protected]>
Cc: "[email protected]"
<[email protected]>
Subject: Re: [Fuego] HTTP ERROR 404 error when 'log' option is clicked
for failed tests in fuego dashboard
Message-ID:

        <[email protected]>

Content-Type: text/plain; charset="us-ascii"

Quoted 7 lines

-----Original Message-----
From: Daniel Sangorrin on Friday, May 19, 2017 12:40 AM

Quoted 2 lines

-----Original Message-----
From: Dhinakar Kalyanasundaram on May 19, 2017 4:25 PM

[email protected]

Quoted 1 line

Subject: RE: RE: RE: RE: RE: RE: RE: [Fuego] HTTP ERROR 404 error when

'log'

Quoted 23 lines

option is clicked for failed tests in fuego dashboard

Quoted 7 lines

Hi Daniel,

I have updated the reference.log file and the test is successful now.

Quoted 8 lines

It was missing the following,

[DaCapo.avrora|le]
1000000

[DaCapo.xalan|le]
1000000

Great, thanks for reporting back.

Quoted 4 lines

I have attached the reference.log file for your reference.

Quoted 7 lines
Quoted 1 line

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 "[email protected]"
$ git config --global sendemail.from "Dhinakar Kalyanasundaram
<[email protected]>"
$ git config --global sendemail.smtpserver mail.xxx.xxx.xx <-- put your

server

Quoted 8 lines
$ 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 [email protected]

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.

Quoted 5 lines
Quoted 1 line

Thanks much, this exercise gave me an insight into the generic parsing

mechanism used by Fuego (parser.py, common.py,

Quoted 3 lines

thresholds.awk etc.).

One question, this 'reference.log' is auto generated by thresholds.awk

so

Quoted 6 lines

the fix should be provided elsewhere otherwise it will

Quoted 3 lines

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

Quoted 2 lines

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 <[email protected]>
To: [email protected], Daniel Sangorrin
<[email protected]>, "Bird, Timothy" <
[email protected]>
Subject: Re: [Fuego] Fuego Digest, Vol 10, Issue 48 Message-ID:

        <CABehs3P5h8a7B6sDxVqshoxCTBO7zp575sw_BtAdaVFzef-g2g@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@Ubuntu-RC510:~/fuego-core$ git send-email -1 --to
[email protected]
/tmp/EipMH1mt3M/0001-java-fix-the-reference.log.patch
(mbox) Adding cc: Dhinakar Kalyanasundaram <[email protected]> from
line
'From: Dhinakar Kalyanasundaram <[email protected]>'
(body) Adding cc: Dhinakar Kalyanasundaram <[email protected]> from
line
'Signed-off-by: Dhinakar Kalyanasundaram <[email protected]>'

From: Dhinakar Kalyanasundaram <[email protected]>
To: [email protected]
Cc: Dhinakar Kalyanasundaram <[email protected]>
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: <[email protected]>
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

Quoted 123 lines · On Fri, May 19, 2017 at 5:30 PM, <[email protected]>…

Send Fuego mailing list submissions to
[email protected]

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
[email protected]

You can reach the person managing the list at
[email protected]

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" <[email protected]>
To: <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [Fuego] HTTP ERROR 404 error when 'log' option is clicked
for failed tests in fuego dashboard
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"

Hi Dhinakar

Quoted 5 lines

-----Original Message-----
From: Dhinakar Kalyanasundaram [mailto:[email protected]]
Sent: Friday, May 19, 2017 4:25 PM
To: Daniel Sangorrin
Cc: Dhinakar Kalyanasundaram; [email protected];

[email protected]

Quoted 1 line

Subject: RE: RE: RE: RE: RE: RE: RE: [Fuego] HTTP ERROR 404 error when

'log' option is clicked for failed tests in fuego dashboard

Quoted 7 lines

Hi Daniel,

I have updated the reference.log file and the test is successful now.

Quoted 8 lines

It was missing the following,

[DaCapo.avrora|le]
1000000

[DaCapo.xalan|le]
1000000

Great, thanks for reporting back.

Quoted 5 lines

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 "[email protected]"
$ git config --global sendemail.from "Dhinakar Kalyanasundaram <
[email protected]>"
$ 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 [email protected]
Quoted 1 line

Thanks much, this exercise gave me an insight into the generic parsing

mechanism used by Fuego (parser.py, common.py,

Quoted 3 lines

thresholds.awk etc.).

One question, this 'reference.log' is auto generated by thresholds.awk

so the fix should be provided elsewhere otherwise it will

Quoted 3 lines

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

Quoted 21 lines

Regards,

Dhinakar,

Senior Technical Manager,

2-07-526, Phoenix Building,

+91-9902007650

Samsung Research Institute, Bangalore.

--------- Original Message ---------

Quoted 11 lines
Quoted 1 line

Sender : Dhinakar Kalyanasundaram <[email protected]> Senior

Technical Manager/SSIR-FDS SW/Samsung Electronics

Quoted 4 lines

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

Quoted 4 lines

To : null<[email protected]>

CC Dhinakar Kalyanasundaram<[email protected]>,

null<fuego@lists.

Quoted 126 lines

linuxfoundation.org>

Quoted 6 lines

Sure Daniel,

I will add the required thresholds to the reference.log and check if it

works.

Quoted 21 lines

Will let you know by today.

Regards,

Dhinakar,

Senior Technical Manager,

2-07-526, Phoenix Building,

+91-9902007650

Samsung Research Institute, Bangalore.

Quoted 7 lines

--------- Original Message ---------

Sender : Daniel Sangorrin <[email protected]>

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

Quoted 2 lines

To : Dhinakar Kalyanasundaram<[email protected]>,

[email protected]

Quoted 7 lines

Hi Dhinakar,

Quoted 2 lines

Traceback (most recent call last):
File "/fuego-core/engine/tests/Benchmark.Java/parser.py", line 42,

in <module>

Quoted 1 line
Quoted 1 line

sys.exit(plib.process_data(ref_section_pat, cur_dict, 'm', 'FPS,

%'))

Quoted 1 line
Quoted 1 line

File "/fuego-core/engine/scripts/parser/common.py", line 92, in

process_data

Quoted 2 lines
Quoted 2 lines

rc = compare(thresholds, test_results, criteria)
File "/fuego-core/engine/scripts/parser/common.py", line 422, in

compare

Quoted 5 lines
Quoted 5 lines

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.

Quoted 1 line
Quoted 1 line

Warning: Permanently added '107.108.83.19' (ECDSA) to the list of

known hosts.

Quoted 1 line
Quoted 1 line

Warning: Permanently added '107.108.83.19' (ECDSA) to the list of

known hosts.

Quoted 1 line
Quoted 1 line

Warning: Permanently added '107.108.83.19' (ECDSA) to the list of

known hosts.

Quoted 1 line
Quoted 1 line

Warning: Permanently added '107.108.83.19' (ECDSA) to the list of

known hosts.

Quoted 2 lines
Quoted 2 lines

Build step 'Execute shell' marked build as failure [description-setter] Description set: <a href="/fuego/userContent/

fuego.logs/Benchmark.Java/ubuntu-x86-

Quoted 5 lines
Quoted 3 lines

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

Quoted 1 line

the reference.log file was not including all of the thresholds. Because

of that some

Quoted 3 lines

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?

Quoted 42 lines
engine/tests/Benchmark.Java/reference.log +4 -0
@@ -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

Quoted 18 lines

Regards,

Dhinakar,

Senior Technical Manager,

2-07-526, Phoenix Building,

+91-9902007650

Samsung Research Institute, Bangalore.

Quoted 8 lines
Quoted 3 lines
Quoted 3 lines

--------- Original Message ---------

Sender : Dhinakar Kalyanasundaram <[email protected]> Senior

Technical Manager/SSIR-FDS SW/Samsung Electronics

Quoted 4 lines
Quoted 4 lines

Date : 2017-05-18 20:44 (GMT+5:30)

Title : RE: RE: RE: RE: [Fuego] HTTP ERROR 404 error when 'log'

option

Quoted 82 lines

is clicked for failed tests in fuego dashboard

Quoted 2 lines
Quoted 2 lines

To : null<[email protected]>, Dhinakar Kalyanasundaram<

[email protected]>,

Quoted 8 lines
Quoted 8 lines

null<[email protected]>

Hi Daniel.

Quoted 5 lines
Quoted 5 lines

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.

Quoted 3 lines
Quoted 3 lines

===== 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

Quoted 2 lines
Quoted 2 lines

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'.

Quoted 4 lines
Quoted 4 lines

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

Quoted 9 lines
Quoted 9 lines

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?

Quoted 2 lines
Quoted 2 lines

Because it will clear every test and results, boards etc. from

Jenkins. I will loose the test history and also custom/internal tests

Quoted 3 lines
Quoted 3 lines

integrated into fuego.

What is the general procedure to upgrade fuego? Is there any link

which I can refer to? Please let me know.

Quoted 19 lines
Quoted 19 lines

Regards,

Dhinakar,

Senior Technical Manager,

2-07-526, Phoenix Building,

+91-9902007650

Samsung Research Institute, Bangalore.

Quoted 7 lines
Quoted 7 lines

--------- Original Message ---------

Sender : Daniel Sangorrin <[email protected]>

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

Quoted 2 lines
Quoted 2 lines

To : Dhinakar Kalyanasundaram<[email protected]>,

[email protected]

Quoted 5 lines
Quoted 5 lines

Hi Dhinakar,

Quoted 13 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

-----Original Message-----
From: Dhinakar Kalyanasundaram [mailto:[email protected]]
Sent: Thursday, May 18, 2017 11:36 AM
To: Daniel Sangorrin; Dhinakar Kalyanasundaram;

[email protected]

Quoted 1 line
Quoted 1 line
Quoted 1 line

Subject: RE: RE: RE: [Fuego] HTTP ERROR 404 error when 'log' option

is clicked for failed tests in fuego dashboard

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

Hi Daniel,

Quoted 1 line

Then you must be running an outdated version of fuego-core in

which

Quoted 71 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

the spec was using "testName" : "Benchmark.java" instead of

"Benchmark.Java".

Quoted 30 lines
Quoted 30 lines
Quoted 4 lines

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

Quoted 18 lines

Regards,

Dhinakar,

Senior Technical Manager,

2-07-526, Phoenix Building,

+91-9902007650

Samsung Research Institute, Bangalore.

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

--------- Original Message ---------

Sender : Daniel Sangorrin <[email protected]>

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

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

To : Dhinakar Kalyanasundaram<[email protected]>,

[email protected]

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

Hi Dhinakar,

Quoted 1 line

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".

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

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

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

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

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

reduce this kind of spelling mistakes.

Thanks,
Daniel

Quoted 1 line

But other tests such as bonnie, cyclictest, dbench, Dhrystone,

ebizzy etc. have passed.

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 9 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

Please check my console log below.

Any environment or path issue?

Started by user anonymous <http://107.108.83.19:8080/

fuego/user/null>

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Building remotely on ubuntu-x86-target <

http://107.108.83.19:8080/

Quoted 18 lines

fuego/computer/ubuntu-x86-target> in workspace /fuego-

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

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

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

+ 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/

Quoted 5 lines

Benchmark.java/java.sh

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

/bin/bash: /fuego-core/engine/tests/Benchmark.java/java.sh: No

such file or directory

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Build step 'Execute shell' marked build as failure [description-setter] Description set: <a

href="/fuego/userContent/

Quoted 32 lines

fuego.logs/Benchmark.java/ubuntu-x86-

Quoted 21 lines
Quoted 21 lines
Quoted 21 lines
Quoted 21 lines

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.

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

--------- Original Message ---------

Sender : Daniel Sangorrin <[email protected]>

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

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

To : Dhinakar Kalyanasundaram<[email protected]>,

Quoted 10 lines

[email protected]

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

Hi Dhinakar,

Quoted 1 line

But I think in case of failure the 'testlog.txt' can be created

and populated with the error reason displayed in 'Console Output'.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

In this case it is, /bin/bash: /fuego-core/engine/tests/

Benchmark.java/java.sh:

Quoted 7 lines

No such file or directory

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

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

Quoted 105 lines

exists as in here:

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

https://bitbucket.org/tbird20d/fuego-
core/src/d449a0a8ed0e1851c29c5895fee0162da59777de/engine/tests/

Benchmark.Java/?at=master

Quoted 26 lines
Quoted 17 lines
Quoted 17 lines
Quoted 17 lines

Thanks,
Daniel

Quoted 13 lines

Regards,

Dhinakar,

Senior Technical Manager,

2-07-526, Phoenix Building,

+91-9902007650

Quoted 9 lines
Quoted 8 lines
Quoted 7 lines
Quoted 6 lines

Samsung Research Institute, Bangalore.

Quoted 1 line

<http://ext.samsung.net/mail/ext/v1/external/status/update?

userid=dhinakar.k&do=bWFpbElEPTIwMTcwNTE3MTE0MzU1ZXBjbXM

Quoted 5 lines
Quoted 4 lines
Quoted 3 lines
Quoted 2 lines
Quoted 1 line

1cDVjOTRkMDZmOTY3ZDBlMWVkYWQ1MDBkNGUyNjdjNjBiNiZyZWNpcGllbnR

BZGRyZXNzPWZ1ZWdvQGxpc3RzLmxpbnV4Zm91bmR

Quoted 11 lines
Quoted 10 lines
Quoted 9 lines
Quoted 8 lines
Quoted 1 line

hdGlvbi5vcmc_>

<http://ext.samsung.net/mail/ext/v1/external/status/update?

userid=dhinakar.k&do=bWFpbElEPTIwMTcwNTE4MDIwMjAxZXBjbXM

Quoted 4 lines
Quoted 3 lines
Quoted 2 lines
Quoted 1 line

1cDcxNDExMjViOTIwYmMyNGExOGZmYzE3NzhiMjdhOTk1MCZyZWNpcGllbnR

BZGRyZXNzPWRhbmllbC5zYW5nb3JyaW5AdG9zaGliYS5

Quoted 10 lines
Quoted 9 lines
Quoted 8 lines
Quoted 1 line

jby5qcA__>

<http://ext.samsung.net/mail/ext/v1/external/status/update?

userid=dhinakar.k&do=bWFpbElEPTIwMTcwNTE4MDIzNTQ4ZXBjbXM

Quoted 3 lines
Quoted 2 lines
Quoted 1 line

1cDQxMjkyYjgyNDRmODg1ZmFmYTVjMjk5MzI4MTc3Mjc2MiZyZWNpcGllbnR

BZGRyZXNzPWRhbmllbC5zYW5nb3JyaW5AdG9zaGliYS5j

Quoted 9 lines
Quoted 8 lines
Quoted 1 line

by5qcA__>

<http://ext.samsung.net/mail/ext/v1/external/status/update?

userid=dhinakar.k&do=bWFpbElEPTIwMTcwNTE4MTUzNDI1ZXBjbXM

Quoted 2 lines
Quoted 1 line

1cDY0ZmNlZGY3ODkzZGY2NTBkYTY1ZDc3MmQ2MTUyMTNhMSZyZWNpcGllbnR

BZGRyZXNzPWRhbmllbC5zYW5nb3JyaW5AdG9zaGliYS

Quoted 11 lines
Quoted 1 line

5jby5qcA__>

Quoted 1 line

<http://ext.samsung.net/mail/ext/v1/external/status/update?

userid=dhinakar.k&do=bWFpbElEPTIwMTcwNTE5MDcyNTE2ZXBjbXM

Quoted 1 line

1cDFmMzY4NDI4OWZmOWVmMDUzNmVkY2E3Yzg3MDY3MWM4YyZyZWNpcGllbnR

BZGRyZXNzPWRhbmllbC5zYW5nb3JyaW5AdG9za

Quoted 1 line

GliYS5jby5qcA__>

------------------------------

Quoted 9 lines

_______________________________________________
Fuego mailing list
[email protected]
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
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/fuego

End of Fuego Digest, Vol 10, Issue 49
*************************************

#2 lore raw
Quoted 6 lines

-----Original Message-----
From: dhinakar k on Friday, May 19, 2017 11:30 PM
Hi Tim,

Quoted 6 lines

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.

I don't see anything in the fuego mailing list moderator queue.

Quoted 2 lines

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.

OK - sounds good. I'm also thinking about creating a non-e-mail way of contributing patches to fuego. I'll announce something on the list if I make any progress on this.

Quoted 3 lines
	Message-Id: <1495223986-12134-1-git-send-email-

[email protected] <mailto:1495223986-12134-1-git-send-email- [email protected]> >

Is this the reference to your e-mail address, that you see in the message sent from your home address?

Quoted 12 lines

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'.

Quoted 7 lines

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 <http://samsung.com> id as well here, may
be because the previous git
update is waiting as well.

It's possible that the e-mail from your gmail account bounced, because it's not subscribed to the fuego mailing list. However, I checked the list settings, and I believe the send filter currently in place allows non-members to post to the list.

You might try sending an e-mail from your gmail account manually, and see if you get a bounce notification from the fuegl mail list server.

Just to clarify, you configured git send-email for using your gmail account, from your home (outside the corporate firewall) and when you tried to send the patch, git said it did so (there were no warning messages or error). Is that right?

If that's correct, did anything show up in your gmail sent folder?
-- Tim

P.S. You might want to look at the section "Use gmail as the smtp server" on this page: https://git-scm.com/docs/git-send-email
and check that your setting matches what is recommended.

author
#3 lore raw

Hi Tim,

Thanks for the response.
I managed to fix the issue with smtp configuration using gmail at home. It seems, because of security issue mail could not be sent (since I was using 2-step verification).
Now I could see the mail I sent in gmail sent folder.
You also would have received the patch that I sent I think.

Thank much again for the support.

Regards,
Dhinakar

Quoted 75 lines · Timothy
Quoted 11 lines

-----Original Message-----
From: dhinakar k on Friday, May 19, 2017 11:30 PM
Hi Tim,

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

Quoted 1 line

queue waiting for moderator approval. Please confirm.

I don't see anything in the fuego mailing list moderator queue.

Quoted 1 line

The below option suggested by you, looks good. I will explore that as we

also

Quoted 1 line

have to use bitbucket in one of your corporate project.

OK - sounds good. I'm also thinking about creating a non-e-mail way of contributing patches to fuego. I'll announce something on the list if I make any progress on this.

Quoted 3 lines
      Message-Id: <1495223986-12134-1-git-send-email-

[email protected] <mailto:1495223986-12134-1-git-send-email- [email protected]> >

Is this the reference to your e-mail address, that you see in the message sent from your home address?

Quoted 12 lines

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'.

Quoted 7 lines

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 <http://samsung.com> id as well here, may
be because the previous git
update is waiting as well.

It's possible that the e-mail from your gmail account bounced, because it's not subscribed to the fuego mailing list. However, I checked the list settings, and I believe the send filter currently in place allows non-members to post to the list.

You might try sending an e-mail from your gmail account manually, and see if you get a bounce notification from the fuegl mail list server.

Just to clarify, you configured git send-email for using your gmail account,
from your home (outside the corporate firewall) and when you tried to send the patch, git said it did so (there were no warning messages or error).
Is that right?

If that's correct, did anything show up in your gmail sent folder?
-- Tim

P.S. You might want to look at the section "Use gmail as the smtp server" on this page: https://git-scm.com/docs/git-send-email
and check that your setting matches what is recommended.