RESOLVED FIXED 63906
[Chromium] LayoutTests/fast/filesystem/workers/simple-persistent-sync.html is failing on chromium worker tests
https://bugs.webkit.org/show_bug.cgi?id=63906
Summary [Chromium] LayoutTests/fast/filesystem/workers/simple-persistent-sync.html is...
Kinuko Yasuda
Reported 2011-07-04 07:14:39 PDT
[Chromium] LayoutTests/fast/filesystem/workers/simple-persistent-sync.html is failing on chromium worker tests. Seems like test expectation data needs to be updated to reflect the recent API change (requestFileSystem -> webkitRequestFileSystem). http://build.chromium.org/p/chromium/builders/Linux%20Tests%20%28dbg%29%282%29/builds/9988 [7363:7373:4838466893:WARNING:resource_dispatcher_host.cc(1590)] Request doesn't seem to have our data chrome/test/ui/ui_layout_test.cc:259: Failure Value of: value.c_str() Actual: "[Worker] webkitRequestFileSystemSync PERSISTENT test. On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". Starting worker: ../resources/simple-persistent-sync.js [Worker] Successfully obtained PERSISTENT FileSystem:file__0:Persistent PASS [Worker] fileSystem.name.length > 0 is true PASS [Worker] fileSystem.root.fullPath is "/" PASS successfullyParsed is true TEST COMPLETE " Expected: expected_result_value.c_str() Which is: "[Worker] requestFileSystemSync PERSISTENT test. On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". Starting worker: ../resources/simple-persistent-sync.js [Worker] Successfully obtained PERSISTENT FileSystem:file__0:Persistent PASS [Worker] fileSystem.name.length > 0 is true PASS [Worker] fileSystem.root.fullPath is "/" PASS successfullyParsed is true TEST COMPLETE "
Attachments
Patch (1.48 KB, patch)
2011-07-04 07:19 PDT, Kinuko Yasuda
no flags
Kinuko Yasuda
Comment 1 2011-07-04 07:19:57 PDT
Kinuko Yasuda
Comment 2 2011-07-05 01:36:08 PDT
Kinuko Yasuda
Comment 3 2011-07-05 01:36:59 PDT
Comment on attachment 99627 [details] Patch Clearing flag as it's basically just an expectation fix for chromium.
Note You need to log in before you can comment on or make changes to this bug.