> -----Original Message-----
> From: Dhinakar Kalyanasundaram  on Friday, October 06, 2017 8:33 AM
> 
> Yes you are right, I did a 'git pull' now and
> Benchmark.lmbench2/fuego_test.sh files got updated.
> 
> But now, I am getting a different error, which I have pasted below.
> 
> It seems some pre-requisites/configuration need to be done. I will look into
> it and try again.

OK - thanks for re-testing this so quickly!

These dependencies are very interesting, and I haven't seen them on my
boards.  Please keep track of any information or dependencies you find,
and let us know about them so we can add them to the test (to help future testers).

In particular, it will be interesting to know any binaries you have to add to your system
to get this test working right (or if you find workarounds for missing binaries).

Hmmm.  Taking a closer look, maybe this is related to the fix I tried.  Can you look at
something for me.  See below.

Thanks!
 -- Tim

> 
> 
> ##### doing fuego phase: run ########
> 
> 
> ==========================================================
> ===========
> 
> 		L M B E N C H   C ON F I G U R A T I O N
> 		----------------------------------------
> 
> You need to configure some parameters to lmbench.  Once you have
> configured
> these parameters, you may do multiple runs by saying
> 
> 	"make rerun"
> 
> in the src subdirectory.
> 
> NOTICE: please do not have any other activity on the system if you can
> help it.  Things like the second hand on your xclock or X perfmeters
> are not so good when benchmarking.  In fact, X is not so good when
> benchmarking.
> 
> ==========================================================
> ===========
> 
> Hang on, we are calculating your timing granularity.
> ./config-run: 39: ./config-run: ../bin/x86_64-Linux/msleep: not found
> ./config-run: 1: ./config-run: ../bin/x86_64-Linux/enough: not found
> OK, it looks like you can time stuff down to  usec resolution.
> 
> Hang on, we are calculating your timing overhead.
> ./config-run: 45: ./config-run: ../bin/x86_64-Linux/msleep: not found
> ./config-run: 1: ./config-run: ../bin/x86_64-Linux/timing_o: not found
> OK, it looks like your gettimeofday() costs  usecs.
> 
> Hang on, we are calculating your loop overhead.
> ./config-run: 51: ./config-run: ../bin/x86_64-Linux/msleep: not found
> ./config-run: 1: ./config-run: ../bin/x86_64-Linux/loop_o: not found
> OK, it looks like your benchmark loop costs  usecs.
> 
> ==========================================================
> ===========

Can you please do the following:
In Jenkins, go to the job page for this test (<board>.<spec>.Benchmark.lmbench2).
and select "Configure", and modify the value of Target_PostCleanup to be "false".
This is in the Build section of the job, in Execute shell, Command text box.
In that same location, uncomment the line:
export FUEGO_DEBUG=1
(that is, remove the leading '#')

Then run the test.  This will produce more a verbose console log and leave the test directory on the board after the test finishes.

After the test, look on the board for the test directory (something like
/home/fuego/fuego.Benchmark.lmbench2, but it will depend on the
BOARD_TESTDIR in your board file.)

Please cd to that directory and do:
 ls bin
 ls bin/*

and report those back to me (and the list).

Please also send the full console log for the test.  I'm specifically looking for the
values used for PREFIX, OS and LMBENCH_OS during the test.

Thanks,
 -- Tim

> If you are running on an MP machine and you want to try running
> multiple copies of lmbench in parallel, you can specify how many here.
> 
> Using this option will make the benchmark run 100x slower (sorry).
> 
> NOTE:  WARNING! This feature is experimental and many results are
> 	known to be incorrect or random!
> 
> MULTIPLE COPIES [default 1] Options to control job placement
> 1) Allow scheduler to place jobs
> 2) Assign each benchmark process with any attendent child processes
>    to its own processor
> 3) Assign each benchmark process with any attendent child processes
>    to its own processor, except that it will be as far as possible
>    from other processes
> 4) Assign each benchmark and attendent processes to their own
>    processors
> 5) Assign each benchmark and attendent processes to their own
>    processors, except that they will be as far as possible from
>    each other and other processes
> 6) Custom placement: you assign each benchmark process with attendent
>    child processes to processors
> 7) Custom placement: you assign each benchmark and attendent
>    processes to processors
> 
> Note: some benchmarks, such as bw_pipe, create attendent child
> processes for each benchmark process.  For example, bw_pipe
> needs a second process to send data down the pipe to be read
> by the benchmark process.  If you have three copies of the
> benchmark process running, then you actually have six processes;
> three attendent child processes sending data down the pipes and
> three benchmark processes reading data and doing the measurements.
> 
> Job placement selection:
> ==========================================================
> ===========
> 
> Several benchmarks operate on a range of memory.  This memory should be
> sized such that it is at least 4 times as big as the external cache[s]
> on your system.   It should be no more than 80% of your physical memory.
> 
> The bigger the range, the more accurate the results, but larger sizes
> take somewhat longer to run the benchmark.
> 
> MB [default 64] Checking to see if you have 64 MB; please wait for a
> moment...
> ./config-run: 1: ./config-run: ../bin/x86_64-Linux/memsize: not found
> ./config-run: 1: ./config-run: ../bin/x86_64-Linux/memsize: not found
> ./config-run: 1: ./config-run: ../bin/x86_64-Linux/memsize: not found
> expr: syntax error
> Hang on, we are calculating your cache line size.
> ./config-run: 202: [: -gt: unexpected operator
> ./config-run: 207: [: -lt: unexpected operator
> ./config-run: 211: [: -lt: unexpected operator
> OK, it looks like your cache line is  bytes.
> 
> ==========================================================
> ===========
> ./config-run: 217: ./config-run: ../bin/x86_64-Linux/msleep: not found
> ./config-run: 1: ./config-run: ../bin/x86_64-Linux/line: not found
> 
> lmbench measures a wide variety of system performance, and the full suite
> of benchmarks can take a long time on some platforms.  Consequently, we
> offer the capability to run only predefined subsets of benchmarks, one
> for operating system specific benchmarks and one for hardware specific
> benchmarks.  We also offer the option of running only selected benchmarks
> which is useful during operating system development.
> 
> Please remember that if you intend to publish the results you either need
> to do a full run or one of the predefined OS or hardware subsets.
> 
> SUBSET (ALL|HARWARE|OS|DEVELOPMENT) [default all]
> ==========================================================
> ===========
> 
> This benchmark measures, by default, memory latency for a number of
> different strides.  That can take a long time and is most useful if you
> are trying to figure out your cache line size or if your cache line size
> is greater than 128 bytes.
> 
> If you are planning on sending in these results, please don't do a fast
> run.
> 
> Answering yes means that we measure memory latency with a 128 byte
> stride.
> 
> FASTMEM [default no]
> ==========================================================
> ===========
> 
> This benchmark measures, by default, file system latency.  That can
> take a long time on systems with old style file systems (i.e., UFS,
> FFS, etc.).  Linux' ext2fs and Sun's tmpfs are fast enough that this
> test is not painful.
> 
> If you are planning on sending in these results, please don't do a fast
> run.
> 
> If you want to skip the file system latency tests, answer "yes" below.
> 
> SLOWFS [default no]
> ==========================================================
> ===========
> 
> This benchmark can measure disk zone bandwidths and seek times.  These
> can
> be turned into whizzy graphs that pretty much tell you everything you might
> need to know about the performance of your disk.
> 
> This takes a while and requires read access to a disk drive.
> Write is not measured, see disk.c to see how if you want to do so.
> 
> If you want to skip the disk tests, hit return below.
> 
> If you want to include disk tests, then specify the path to the disk
> device, such as /dev/sda.  For each disk that is readable, you'll be
> prompted for a one line description of the drive, i.e.,
> 
> 	Iomega IDE ZIP
> or
> 	HP C3725S 2GB on 10MB/sec NCR SCSI bus
> 
> DISKS [default none]
> ==========================================================
> ===========
> 
> If you are running on an idle network and there are other, identically
> configured systems, on the same wire (no gateway between you and them),
> and you have rsh access to them, then you should run the network part
> of the benchmarks to them.  Please specify any such systems as a space
> separated list such as: ether-host fddi-host hippi-host.
> 
> REMOTE [default none]
> ==========================================================
> ===========
> 
> Calculating mhz, please wait for a moment...
> ./config-run: 1: ./config-run: ../bin/x86_64-Linux/mhz: not found
> I think your CPU mhz is
> 
> 
> 
> but I am frequently wrong.  If that is the wrong Mhz, type in your
> best guess as to your processor speed.  It doesn't have to be exact,
> but if you know it is around 800, say 800.
> 
> Please note that some processors, such as the P4, have a core which
> is double-clocked, so on those processors the reported clock speed
> will be roughly double the advertised clock rate.  For example, a
> 1.8GHz P4 may be reported as a 3592MHz processor.
> 
> Processor mhz [default ]
> ==========================================================
> ===========
> 
> We need a place to store a  Mbyte file as well as create and delete a
> large number of small files.  We default to /usr/tmp.  If /usr/tmp is a
> memory resident file system (i.e., tmpfs), pick a different place.
> Please specify a directory that has enough space and is a local file
> system.
> 
> FSDIR [default /var/tmp]
> ==========================================================
> ===========
> 
> lmbench outputs status information as it runs various benchmarks.
> By default this output is sent to /dev/tty, but you may redirect
> it to any file you wish (such as /dev/null...).
> 
> Status output file [default /dev/tty]
> ==========================================================
> ===========
> 
> There is a database of benchmark results that is shipped with new
> releases of lmbench.  Your results can be included in the database
> if you wish.  The more results the better, especially if they include
> remote networking.  If your results are interesting, i.e., for a new
> fast box, they may be made available on the lmbench web page, which is
> 
> 	http://www.bitmover.com/lmbench
> 
> Mail results [default yes] OK, no results mailed.
> ==========================================================
> ===========
> 
> Confguration done, thanks.
> 
> There is a mailing list for discussing lmbench hosted at BitMover.
> Send mail to majordomo@bitmover.com to join the list.
> 
> ./config-run: 743: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 744: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 745: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 746: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 747: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 748: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 749: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 750: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 751: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 752: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 753: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 754: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 755: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 756: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 757: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 758: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 759: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 760: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 761: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 762: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 763: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 764: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 765: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 766: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 767: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 768: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 769: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 770: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 771: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 772: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 773: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 774: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 775: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 776: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 777: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 778: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 779: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 780: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 781: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 782: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 783: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 784: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 785: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 786: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> ./config-run: 787: ./config-run: cannot create ../bin/x86_64-
> Linux/CONFIG.Ubuntu-1604-64bit: Directory nonexistent
> No config file?
> in signal_handler
> scp: /home/a/fuego.Benchmark.lmbench2/Benchmark.lmbench2.log: No
> such file or directory
> Build step 'Execute shell' marked build as failure
> [description-setter] Description set:  <a
> href="/fuego/userContent/fuego.logs/Benchmark.lmbench2/TRAV-
> Ethernet-x86.default.5.5/testlog.txt">testlog</a> <a
> href="/fuego/userContent/fuego.logs/Benchmark.lmbench2/TRAV-
> Ethernet-x86.default.5.5/run.json">run.json</a> <a
> href="/fuego/userContent/fuego.logs/Benchmark.lmbench2/TRAV-
> Ethernet-x86.default.5.5/consolelog.txt">fuegolog</a> <a
> href="/fuego/userContent/fuego.logs/Benchmark.lmbench2/TRAV-
> Ethernet-x86.default.5.5/devlog.txt">devlog</a> <a
> href="/fuego/userContent/fuego.logs/Benchmark.lmbench2/TRAV-
> Ethernet-x86.default.5.5/prolog.sh">prolog.sh</a>
> Finished: FAILURE
> 
> 
> 
> Regards,
> 
> Dhinakar,
> 
> Senior Technical Manager,
> 
> 2-07-526, Phoenix Building,
> 
> +91-9902007650
> 
> Samsung Research Institute, Bangalore.
> 
> 
> 
> 
> 
> --------- Original Message ---------
> 
> Sender : Bird, Timothy <Tim.Bird@sony.com>
> 
> Date : 2017-10-06 20:49 (GMT+5:30)
> 
> Title : RE: [Fuego] Benchmark.lmbench2 failed during 'fuego phase: run' stage
> on x86 64-bit target
> 
> To : Dhinakar Kalyanasundaram<dhinakar.k@samsung.com>,
> null<fuego@lists.linuxfoundation.org>
> 
> 
> 
> > -----Original Message-----
> > From Dhinakar Kalyanasundaram on Friday, October 06, 2017 5:30 AM
> >
> > Benchmark.lmbench2 failed during 'fuego phase: run' stage on x86 64-bit
> > target.
> >
> > The execution log has been pasted below for reference.
> >
> > Please let me know how to fix it. Thanks in advance.
> 
> This is fixed with the following commit in my 'next' branch on bitbucket:
> https://bitbucket.org/tbird20d/fuego-
> core/commits/7f5c0cdb05c189a6ef89524ce29869b989dc84bf
> 
> Please do a 'git pull' and try this test again.
> 
> Note that although I made this fix on Tuesday, I pushed it to bitbucket just
> now (2 minutes ago).
> So even if you've pulled in the last 10 minutes, you may need to pull again.
> Sorry about that.
> 
> Thanks for the bug report.  They are keeping me on my toes!
>  -- Tim
> 
> 
> >
> >
> > ##### doing fuego phase: build ########
> > The test is already built
> > Fuego test_build duration=0 seconds
> > ##### doing fuego phase: deploy ########
> > ##### doing fuego phase: pre_deploy ########
> > ##### doing fuego phase: test_deploy ########
> > ##### doing fuego phase: post_deploy ########
> > ##### doing fuego phase: run ########
> > bash: line 1: bw_mem: command not found
> > bash: line 2: bw_mmap_rd: command not found
> > bash: line 3: bw_pipe: command not found
> > bash: line 4: bw_tcp: command not found
> > bash: line 5: bw_unix: command not found
> > bash: line 6: cache: command not found
> > bash: line 7: disk: command not found
> > bash: line 8: enough: command not found
> > bash: line 9: flushdisk: command not found
> > bash: line 10: getopt.o: command not found
> > bash: line 11: hello: command not found
> > bash: line 12: lat_cmd: command not found
> > bash: line 13: lat_connect: command not found
> > bash: line 14: lat_ctx: command not found
> > bash: line 15: lat_dram_page: command not found
> > bash: line 16: lat_fcntl: command not found
> > bash: line 17: lat_fifo: command not found
> > bash: line 18: lat_fs: command not found
> > bash: line 19: lat_http: command not found
> > bash: line 20: lat_mem_rd: command not found
> > bash: line 21: lat_mmap: command not found
> > bash: line 22: lat_ops: command not found
> > bash: line 23: lat_pagefault: command not found
> > bash: line 24: lat_pipe: command not found
> > bash: line 25: lat_pmake: command not found
> > bash: line 26: lat_proc: command not found
> > bash: line 27: lat_rand: command not found
> > bash: line 28: lat_rpc: command not found
> > bash: line 29: lat_select: command not found
> > bash: line 30: lat_sem: command not found
> > bash: line 31: lat_sig: command not found
> > bash: line 32: lat_syscall: command not found
> > bash: line 33: lat_tcp: command not found
> > bash: line 34: lat_udp: command not found
> > bash: line 35: lat_unix: command not found
> > bash: line 36: lat_unix_connect: command not found
> > bash: line 37: lat_usleep: command not found
> > bash: line 38: lib_debug.o: command not found
> > bash: line 39: lib_mem.o: command not found
> > bash: line 40: lib_sched.o: command not found
> > bash: line 41: lib_stats.o: command not found
> > bash: line 42: lib_tcp.o: command not found
> > bash: line 43: lib_timing.o: command not found
> > bash: line 44: lib_udp.o: command not found
> > bash: line 45: lib_unix.o: command not found
> >
> > bash: line 47: lmbench: command not found
> > bash: line 48: lmbench.a: command not found
> > bash: line 49: lmdd: command not found
> > bash: line 50: lmhttp: command not found
> > bash: line 51: loop_o: command not found
> > bash: line 52: memsize: command not found
> > bash: line 53: mhz: command not found
> > bash: line 54: msleep: command not found
> > bash: line 55: par_mem: command not found
> > bash: line 56: par_ops: command not found
> > Version: ImageMagick 6.8.9-9 Q16 x86_64 2017-07-31
> > http://www.imagemagick.org <http://www.imagemagick.org/>
> > Copyright: Copyright (C) 1999-2014 ImageMagick Studio LLC
> > Features: DPC Modules OpenMP
> > Delegates: bzlib cairo djvu fftw fontconfig freetype jbig jng jpeg lcms lqr ltdl
> > lzma openexr pangocairo png rsvg tiff wmf x xml zlib
> >
> > Usage: stream [options ...] input-image raw-image
> >
> > Image Settings:
> >   -authenticate password
> >                        decipher image with this password
> >   -channel type        apply option to select image channels
> >   -colorspace type     alternate image colorspace
> >   -compress type       type of pixel compression when writing the image
> >   -define format:option
> >                        define one or more image format options
> >   -density geometry    horizontal and vertical density of the image
> >   -depth value         image depth
> >   -extract geometry    extract area from image
> >   -identify            identify the format and characteristics of the image
> >   -interlace type      type of image interlacing scheme
> >   -interpolate method  pixel color interpolation method
> >   -limit type value    pixel cache resource limit
> >   -map components      one or more pixel components
> >   -monitor             monitor progress
> >   -quantize colorspace reduce colors in this colorspace
> >   -quiet               suppress all warning messages
> >   -regard-warnings     pay attention to warning messages
> >   -respect-parentheses settings remain in effect until parenthesis boundary
> >   -sampling-factor geometry
> >                        horizontal and vertical sampling factor
> >   -seed value          seed a new sequence of pseudo-random numbers
> >   -set attribute value set an image attribute
> >   -size geometry       width and height of image
> >   -storage-type type   pixel storage type
> >   -synchronize         synchronize image to storage device
> >   -taint               declare the image as modified
> >   -transparent-color color
> >                        transparent color
> >   -verbose             print detailed information about the image
> >   -virtual-pixel method
> >                        virtual pixel access method
> >
> > Miscellaneous Options:
> >   -debug events        display copious debugging information
> >   -help                print program options
> >   -list type           print a list of supported option arguments
> >   -log format          format of debugging information
> >   -version             print version information
> >
> > By default, the image format of `file' is determined by its magic
> > number.  To specify a particular image format, precede the filename
> > with an image format name and a colon (i.e. ps:image) or specify the
> > image type as the filename suffix (i.e. image.ps).  Specify 'file' as
> > '-' for standard input or output.
> > bash: line 58: timing_o: command not found
> > bash: line 59: tlb: command not found
> > in signal_handler
> > scp: /home/a/fuego.Benchmark.lmbench2/Benchmark.lmbench2.log: No
> > such file or directory
> > Build step 'Execute shell' marked build as failure
> > [description-setter] Description set:  <a
> > href="/fuego/userContent/fuego.logs/Benchmark.lmbench2/TRAV-
> > Ethernet-x86.default.3.3/testlog.txt">testlog</a> <a
> > href="/fuego/userContent/fuego.logs/Benchmark.lmbench2/TRAV-
> > Ethernet-x86.default.3.3/run.json">run.json</a> <a
> > href="/fuego/userContent/fuego.logs/Benchmark.lmbench2/TRAV-
> > Ethernet-x86.default.3.3/consolelog.txt">fuegolog</a> <a
> > href="/fuego/userContent/fuego.logs/Benchmark.lmbench2/TRAV-
> > Ethernet-x86.default.3.3/devlog.txt">devlog</a> <a
> > href="/fuego/userContent/fuego.logs/Benchmark.lmbench2/TRAV-
> > Ethernet-x86.default.3.3/prolog.sh">prolog.sh</a>
> > Finished: FAILURE
> >
> >
> > 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=dhina
> >
> kar.k&do=bWFpbElEPTIwMTcxMDA2MTIyOTM3ZXBjbXM1cDcxODRhOGJjZD
> >
> dmYThlZTc2OGNhYWMwZGFkNzJjZGUxYyZyZWNpcGllbnRBZGRyZXNzPWZ1Z
> > WdvQGxpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmc_>
> 
> 
> 
> 
> 
> 
> 
> <http://ext.samsung.net/mail/ext/v1/external/status/update?userid=dhina
> kar.k&do=bWFpbElEPTIwMTcxMDA2MTUzMzAyZXBjbXM1cDIwNTUwOGNh
> YzFkODRjMTdjZmI1YzMxNDIwNWZiODg0YiZyZWNpcGllbnRBZGRyZXNzPVRp
> bS5CaXJkQHNvbnkuY29t>