Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Porting results to a file or as UI element #17

Open
GoogleCodeExporter opened this issue Apr 11, 2015 · 5 comments
Open

Porting results to a file or as UI element #17

GoogleCodeExporter opened this issue Apr 11, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

We run octane for our chip validation.
we run using automation, results are generated in log, as our log buffer is too 
low, results are overwritten by different logs. 
Can you guys make results as ui elements.
we are using uiautomator dump in android to dump results UI and parse the 
results.
or provide any other way to parse results.


Original issue reported on code.google.com by [email protected] on 10 Apr 2014 at 8:24

@GoogleCodeExporter
Copy link
Author

Sounds like a good idea. I guess the results don't have to be visible but just 
easier to parse? In that case, would a list in a comment in the html file do 
it? 
Or better a normal html element which is not normally visible (say, same color 
as background), so we don't change the page appearance?

Original comment by [email protected] on 10 Apr 2014 at 12:22

@GoogleCodeExporter
Copy link
Author

Currently it displaying as a comment is log.
If it saves all results  as one element in html, it will be good for
parsing.

example like sunspider, kraken etc.

Original comment by [email protected] on 10 Apr 2014 at 1:33

@GoogleCodeExporter
Copy link
Author

Any Update on this.

Original comment by [email protected] on 3 May 2014 at 11:21

@GoogleCodeExporter
Copy link
Author

hi ,

Any update on this

Original comment by [email protected] on 6 Oct 2014 at 5:05

@bathepawan
Copy link

Octane v2 Benchmark dumps results in logcat,

You can use filter like
adb logcat -v threadtime -s chromium:I
to get results.

Overall result is not in logcat and that can be calculated from geometric mean of individual results
I hope this helps..

08-01 11:46:38.150 14696 14696 I chromium: [INFO:CONSOLE(61)] "EarleyBoyer: 6866", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:46:41.709 14696 14696 I chromium: [INFO:CONSOLE(61)] "RegExp: 825", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:46:44.254 14696 14696 I chromium: [INFO:CONSOLE(61)] "Splay: 3346", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:46:44.258 14696 14696 I chromium: [INFO:CONSOLE(61)] "SplayLatency: 4176", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:46:46.358 14696 14696 I chromium: [INFO:CONSOLE(61)] "NavierStokes: 5184", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:46:48.993 14696 14696 I chromium: [INFO:CONSOLE(61)] "PdfJS: 3405", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:46:53.746 14696 14696 I chromium: [INFO:CONSOLE(61)] "Mandreel: 2639", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:46:53.748 14696 14696 I chromium: [INFO:CONSOLE(61)] "MandreelLatency: 1935", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:46:56.400 14696 14696 I chromium: [INFO:CONSOLE(61)] "Gameboy: 8463", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:46:58.584 14696 14696 I chromium: [INFO:CONSOLE(61)] "CodeLoad: 3328", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:47:00.894 14696 14696 I chromium: [INFO:CONSOLE(61)] "Box2D: 2939", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:47:12.068 14696 14696 I chromium: [INFO:CONSOLE(61)] "zlib: 13804", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)
08-01 11:47:32.323 14696 14696 I chromium: [INFO:CONSOLE(61)] "Typescript: 6322", source: http://octane-benchmark.googlecode.com/svn/latest/index.html (61)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants