All of lore.kernel.org
 help / color / mirror / Atom feed
* [Fuego] Path of testlog & run.json under Build History
       [not found]                 ` <CABehs3MVSaDghv=He9Lnzf=Q28eDnCb_BzQrJRX02E-bvxtCpw@mail.gmail.com>
@ 2017-08-21 12:29                   ` dhinakar k
  2017-08-23  1:09                     ` Bird, Timothy
  0 siblings, 1 reply; 3+ messages in thread
From: dhinakar k @ 2017-08-21 12:29 UTC (permalink / raw)
  To: fuego

[-- Attachment #1: Type: text/plain, Size: 400 bytes --]

Hi,

I would like to know from where does Fuego pick up the path of 'testlog',
'run.json' files? It is like the one given below that is published:
url:8080/fuego/userContent/fuego.logs/Benchmark.ffsb/<testname>/testlog.txt

I checked parsers under fuego-core/engine/scripts folder but couldn't find
in which parser or shell script it is implemented. Can anyone please let me
know?

Regards,
Dhinakar

[-- Attachment #2: Type: text/html, Size: 655 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Fuego] Path of testlog & run.json under Build History
  2017-08-21 12:29                   ` [Fuego] Path of testlog & run.json under Build History dhinakar k
@ 2017-08-23  1:09                     ` Bird, Timothy
  2017-08-23  2:04                       ` dhinakar k
  0 siblings, 1 reply; 3+ messages in thread
From: Bird, Timothy @ 2017-08-23  1:09 UTC (permalink / raw)
  To: dhinakar k, fuego



> -----Original Message-----
> From: dhinakar k
> I would like to know from where does Fuego pick up the path of 'testlog',
> 'run.json' files? It is like the one given below that is published:
> url:8080/fuego/userContent/fuego.logs/Benchmark.ffsb/<testname>/testlo
> g.txt
> 
> I checked parsers under fuego-core/engine/scripts folder but couldn't find in
> which parser or shell script it is implemented. Can anyone please let me
> know?

LOGDIR is  defined (and exported) from fuego-core/engine/scripts/overlays.sh
in the function set_overlay_vars().  It is also defined in functions.sh in the
function pre_test().

References to materials related to run output (such as testlog.txt and run.json)
are then relative to this environment variable.  For example in Fuego 1.1 functions.sh:
    cat > $LOGDIR/run.json <<RUN_JSON_TEMPLATE
or:
   get $BOARD_TESTDIR/fuego.$1/$1.log ${LOGDIR}/testlog.txt
 
Sorry for the slow response - was watching an eclipse :-)
 -- Tim


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Fuego] Path of testlog & run.json under Build History
  2017-08-23  1:09                     ` Bird, Timothy
@ 2017-08-23  2:04                       ` dhinakar k
  0 siblings, 0 replies; 3+ messages in thread
From: dhinakar k @ 2017-08-23  2:04 UTC (permalink / raw)
  To: Bird, Timothy; +Cc: fuego

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

Thank you very much Tim for the response.
It must have been a memorable moment watching total solar eclipse.
I saw the video it was amazing.

Regards,
Dhinakar

On Wed, Aug 23, 2017 at 6:39 AM, Bird, Timothy <Tim.Bird@sony.com> wrote:

>
>
> > -----Original Message-----
> > From: dhinakar k
> > I would like to know from where does Fuego pick up the path of 'testlog',
> > 'run.json' files? It is like the one given below that is published:
> > url:8080/fuego/userContent/fuego.logs/Benchmark.ffsb/<testname>/testlo
> > g.txt
> >
> > I checked parsers under fuego-core/engine/scripts folder but couldn't
> find in
> > which parser or shell script it is implemented. Can anyone please let me
> > know?
>
> LOGDIR is  defined (and exported) from fuego-core/engine/scripts/
> overlays.sh
> in the function set_overlay_vars().  It is also defined in functions.sh in
> the
> function pre_test().
>
> References to materials related to run output (such as testlog.txt and
> run.json)
> are then relative to this environment variable.  For example in Fuego 1.1
> functions.sh:
>     cat > $LOGDIR/run.json <<RUN_JSON_TEMPLATE
> or:
>    get $BOARD_TESTDIR/fuego.$1/$1.log ${LOGDIR}/testlog.txt
>
> Sorry for the slow response - was watching an eclipse :-)
>  -- Tim
>
>

[-- Attachment #2: Type: text/html, Size: 1796 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-08-23  2:04 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CABehs3OQ2c5wwgSKELSz8qbGZ804CmnUTJprjPi9BOWFT0yRfg@mail.gmail.com>
     [not found] ` <CABehs3PutuxMhB88OT6fmKv14Bd-JtBX1qbn8z4wBLPGOoQRzw@mail.gmail.com>
     [not found]   ` <CABehs3OpLRsFDcNWwwHd1=5AWjMnTk6y1u6YEvcnHJnp9fJVog@mail.gmail.com>
     [not found]     ` <CABehs3PdU02Brn4zSW62_X++Y_NVYU3dOAvZZdzgaRvwseSr0Q@mail.gmail.com>
     [not found]       ` <CABehs3OgG0sCFbc1brQQ0=qTyhdAz436Pc2XfT9sOJE==f0z9A@mail.gmail.com>
     [not found]         ` <CABehs3ON_n8wyewve=sEMExa=k_XFb0FuLD9NsazGrofSDW-YQ@mail.gmail.com>
     [not found]           ` <CABehs3NE_88SqQwWjFCg62rLuZV7WXmQq9O7AsQ4Ybx0rZzUTA@mail.gmail.com>
     [not found]             ` <CABehs3M8Lajcnm_YoBp=hjCP9UokYgA_zpFOyf_ATwUGQs7tDg@mail.gmail.com>
     [not found]               ` <CABehs3M3z6YfjOMe28n3-+w7aGmTopTXNYfKJCppxW9UO37opw@mail.gmail.com>
     [not found]                 ` <CABehs3MVSaDghv=He9Lnzf=Q28eDnCb_BzQrJRX02E-bvxtCpw@mail.gmail.com>
2017-08-21 12:29                   ` [Fuego] Path of testlog & run.json under Build History dhinakar k
2017-08-23  1:09                     ` Bird, Timothy
2017-08-23  2:04                       ` dhinakar k

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.