780602 - Intermittent Android test_webgl_conformance_test_suite.html | [conformance/glsl/implicit/subtract_int_mat3.vert.html] Timeout in this test page

Status: RESOLVED INVALID

(Core :: Graphics: CanvasWebGL, defect)

Description

[Ed Morley [:emorley]]

Android Tegra 250 mozilla-inbound opt test mochitest-1 on 2012-08-05 18:08:51 PDT for push 22e600473209

slave: tegra-159

https://tbpl.mozilla.org/php/getParsedLog.php?id=14149800&tree=Mozilla-Inbound

{
42957 INFO TEST-INFO | /tests/content/canvas/test/webgl/test_webgl_conformance_test_suite.html | [conformance/glsl/implicit/subtract_int_mat3.vert.html] (WebGL mochitest) Starting test page
42958 INFO TEST-PASS | /tests/content/canvas/test/webgl/test_webgl_conformance_test_suite.html | [conformance/glsl/implicit/subtract_int_mat3.vert.html] Test passed - finishTest epilogue onload: 1344191262171
failed to validate file when downloading /mnt/sdcard/tests/logs/mochitest.log!
42959 ERROR TEST-UNEXPECTED-FAIL | /tests/content/canvas/test/webgl/test_webgl_conformance_test_suite.html | [conformance/glsl/implicit/subtract_int_mat3.vert.html] Timeout in this test page
}

Comment 1

[Benoit Jacob [:bjacob] (mostly away)]

Hm, this lime is the log (in comment 0) is probably the real issue:

failed to validate file when downloading /mnt/sdcard/tests/logs/mochitest.log!

Joel?

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

that is expected and in almost all logs.  That message is printed out when we pull the logfile from the device (every 5 seconds) and do a hash on it to make sure we got the entire file.  If a test case writes to the file during the time we are transferring it, then we print that message.

This looks like a legitimate timeout.  Remember on android we run the tests from a remote webserver, so we do more stuff than just load a file and expect it to work.

Comment 3

[Benoit Jacob [:bjacob] (mostly away)]

OK, so is this INVALID? or WONTFIX?

Comment 4

[Joel Maher ( :jmaher ) (UTC -8)]

this is a real bug, the message "failed to validate file when downloading /mnt/sdcard/tests/logs/mochitest.log!" is what is expected.

Comment 5

[Benoit Jacob [:bjacob] (mostly away)]

OK, I see.

Without stderr output in the mochitest log, this is really hard to debug. Any chance we could get stderr?

Comment 6

[Joel Maher ( :jmaher ) (UTC -8)]

is stderr logcat?  If so, we get logcat, just a limited amount so we can parse the logfiles in a sane fashion.  To work around this you can send a hacked up version of android.json to the try server or run it locally.

It is probably easier for me to run it locally if you let me know where stderr is.

Comment 7

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

This bug was observed only on one or more of the six machines listed in
bug 787281 comment 11, which seem likely to have bad memory, disk, or
other hardware problem, based on the rate of failures on those machines
and the types of failures observed.

Therefore I'm marking this bug invalid, though it should be reopened if
it occurs on other (more reliable) hardware.