If you build a ChromeOS image for daisy using the LLVM compiler, load the image onto a daisy Chromebook and try to run the Kraken telemetry test on that Chromebook, it hangs. GCC-built images do not have this problem. python /var/cache/chromeos-cache/distfiles/target/chrome-src-internal/src/tools/perf/run_benchmark --browser=cros-chrome --remote=chromeos2-row5-rack4-host6.cros kraken [ RUN ] http://krakenbenchmark.mozilla.org/kraken-1.1/driver.html Traceback (most recent call last): File "/var/cache/chromeos-cache/distfiles/target/chrome-src-internal/src/tools/telemetry/telemetry/internal/story_runner.py", line 83, in _RunStoryAndProcessErrorIfNeeded state.RunStory(results) File "/var/cache/chromeos-cache/distfiles/target/chrome-src-internal/src/tools/telemetry/telemetry/page/shared_page_state.py", line 300, in RunStory self._current_page, self._current_tab, results) File "/var/cache/chromeos-cache/distfiles/target/chrome-src-internal/src/tools/perf/benchmarks/kraken.py", line 88, in ValidateAndMeasurePage 'document.title.indexOf("Results") != -1', 700) File "/var/cache/chromeos-cache/distfiles/target/chrome-src-internal/src/tools/telemetry/telemetry/internal/browser/web_contents.py", line 129, in WaitForJavaScriptExpression """)) TimeoutException: Timed out while waiting 700s for IsJavaScriptExpressionTrue. JavaScript |this|: external: [object Object] chrome: [object Object] document: [object HTMLDocument] tests: ai-astar,audio-beat-detection,audio-dft,audio-fft,audio-oscillator,imaging-gaussian-blur,imaging-darkroom,imaging-desaturate,json-parse-financial,json-stringify-tinderbox,stanford-crypto-aes,stanford-crypto-ccm,stanford-crypto-pbkdf2,stanford-crypto-sha256-iterative categories: ai,audio,imaging,json,stanford testContents: <!DOCTYPE html> <head> <meta charset=utf8> ... Then comes a bunch of screen dumps of source files: Captured full dump in a file, which is too big to attach to this bug. Email me if you want a copy of it.
This bug may be a copy of 25417; more investigation is needed to verify that.
Hi Caroline, I'm afraid this bug report doesn't have enough detail to investigate. From the description it could either be a compiler malfunction or undefined/implementation defined behaviour being relied upon by the program. I'm afraid compiling up a ChromeOS image and obtaining hardware is beyond the expectataion for a bug investigation on our side. Unfortunately you'll have to investigate further before we can help. Cheers, James
I will do that.