Bug 193856
| Summary: | REGRESSION: run-webkit-tests --ios-simulator --reset-results does not emit message of where it wrote the result | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Daniel Bates <dbates> |
| Component: | Tools / Tests | Assignee: | Jonathan Bedard <jbedard> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | lforschler, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar, Regression |
| Version: | WebKit Local Build | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 12 | ||
Daniel Bates
Seen with WebKit r240438.
I could have sworn that run-webkit-tests --ios-simulator --reset-results X use to emit a message when it would write out new results. I tried it today to generate new results for fast/events/ios/key-events-meta-alt-combinations.html after making amendments to the patch for bug #193452 and run-webkit-tests just emitted:
[[
Running 0 tests for iPhone SE running None
The test ran as expected.
]]
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/47565898>
Daniel Bates
Actually, it does emit a message. It's just ABOVE the message about the test not being run on iPhone SE!
[[
Running 1 test for iPad (6th generation) running None
Running 1 WebKitTestRunnerApp.app.
Writing new expected result "fast/events/ios/key-events-meta-alt-combinations-expected.txt"
...
Baseline search path: ...
Running 0 tests for iPhone SE running None
The test ran as expected.
]]
Daniel Bates
*** This bug has been marked as a duplicate of bug 193857 ***