WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
89717
[chromium] Layout Test fast/speech/scripted/speechgrammar-basics.html is flaky
https://bugs.webkit.org/show_bug.cgi?id=89717
Summary
[chromium] Layout Test fast/speech/scripted/speechgrammar-basics.html is flaky
Kenneth Russell
Reported
2012-06-21 17:23:10 PDT
The following layout test is flaky in Chromium on Windows, Mac and Linux: fast/speech/scripted/speechgrammar-basics.html See:
http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=fast%2Fspeech%2Fscripted%2Fspeechgrammar-basics.html
It's gotten significantly flakier on 32-bit Linux recently. It's failing in roughly every other build:
http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Linux%2032
http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Linux%2032/builds/20016
http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Linux%2032/builds/20018
http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Linux%2032/builds/20020
Unfortunately I don't have a guess about a probable cause. The first recent build where it appeared to start crashing was:
http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Linux%2032/builds/20014
I'm going to suppress this failure in the test expectations for the moment.
Attachments
Add attachment
proposed patch, testcase, etc.
Kenneth Russell
Comment 1
2012-06-21 17:54:05 PDT
Committed
r120986
: <
http://trac.webkit.org/changeset/120986
>
Hans Wennborg
Comment 2
2012-06-28 03:21:44 PDT
I still haven't been able to reproduce this locally, but this is the interesting bit of output from the bot: 16:22:22.845 31571 worker/3 fast/speech/scripted/navigate-away.html passed 16:22:22.892 31571 worker/3 fast/speech/scripted/speechgrammar-basics.html crashed, stack trace: 16:22:22.892 31571 base::debug::StackTrace::StackTrace() [0x82c6874] 16:22:22.893 31571 base::(anonymous namespace)::StackDumpSignalHandler() [0x82b175d] 16:22:22.893 31571 0xb7802400 16:22:22.893 31571 WebCore::EventTarget::fireEventListeners() [0x823e555] 16:22:22.893 31571 WebCore::EventTarget::fireEventListeners() [0x823e711] 16:22:22.893 31571 WebCore::EventTarget::dispatchEvent() [0x823e786] 16:22:22.893 31571 WebCore::SpeechRecognition::didEnd() [0x88e1555] 16:22:22.893 31571 WebKit::SpeechRecognitionClientProxy::didEnd() [0x80f5606] 16:22:22.893 31571 (anonymous namespace)::ClientCallTask::run() [0x8085171] 16:22:22.893 31571 MockWebSpeechRecognizer::StepTask::runIfValid() [0x80854f2] 16:22:22.893 31571 MethodTask<>::run() [0x8085288] 16:22:22.893 31571 invokeTask() [0x808ae79] 16:22:22.893 31571 base::internal::Invoker<>::Run() [0x81c5809] 16:22:22.893 31571 MessageLoop::RunTask() [0x82a48b0] 16:22:22.893 31571 MessageLoop::DeferOrRunPendingTask() [0x82a4f51] 16:22:22.893 31571 MessageLoop::DoWork() [0x82a52b1] 16:22:22.893 31571 base::MessagePumpGlib::HandleDispatch() [0x82c0628] 16:22:22.893 31571 (anonymous namespace)::WorkSourceDispatch() [0x82c0667] 16:22:22.893 31571 0xb75f75e5 16:22:22.893 31571 0xb75fb2d8 16:22:22.893 31571 0xb75fb4b8 16:22:22.893 31571 base::MessagePumpGlib::RunWithDispatcher() [0x82c0af9] 16:22:22.894 31571 base::MessagePumpGlib::Run() [0x82c068e] 16:22:22.894 31571 MessageLoop::RunInternal() [0x82a04de] 16:22:22.894 31571 MessageLoop::Run() [0x82a05f9] 16:22:22.894 31571 webkit_support::RunMessageLoop() [0x81c5faf] 16:22:22.894 31571 TestShell::waitTestFinished() [0x80908d9] 16:22:22.894 31571 TestShell::runFileTest() [0x808ee32] 16:22:22.894 31571 runTest() [0x8067daa] 16:22:22.894 31571 main [0x806843b] 16:22:22.894 31571 0xb6affbd6 16:22:22.894 31571 0x805c311 16:22:22.896 31548 fast/speech/scripted/speechgrammar-basics.html -> unexpected crash I think it's navigate-away.html that's triggering the problem really, but it ends up crashing speechgrammar-basics.html which is run afterwards. Probably something is not right with
http://trac.webkit.org/changeset/120913
Hans Wennborg
Comment 3
2012-06-28 07:09:07 PDT
I think the patch in
bug 90176
should fix this.
Hans Wennborg
Comment 4
2012-06-29 00:45:13 PDT
Seems to be fixed by
bug 90176
.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug