WebKit Bugzilla
New
Browse
Search+
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
141718
[iOS] run-webkit-tests should check that simctl can boot and shutdown simulator device before running tests
https://bugs.webkit.org/show_bug.cgi?id=141718
Summary
[iOS] run-webkit-tests should check that simctl can boot and shutdown simulat...
Daniel Bates
Reported
2015-02-17 12:12:31 PST
We should ensure that simctl can boot and shutdown the testing device before running layout tests to avoid unnecessarily spending time running tests with a simulator device or iOS Simulator that is in a bad state.
Attachments
Patch
(4.10 KB, patch)
2015-02-17 12:21 PST
,
Daniel Bates
no flags
Details
Formatted Diff
Diff
View All
Add attachment
proposed patch, testcase, etc.
Daniel Bates
Comment 1
2015-02-17 12:21:13 PST
Created
attachment 246759
[details]
Patch
Alex Christensen
Comment 2
2015-02-17 12:55:06 PST
Comment on
attachment 246759
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=246759&action=review
Looks good. Minor change suggestions and questions:
> Tools/ChangeLog:1 > 2015-02-17 Daniel Bates <
dabates@apple.com
>
This patch probably does not apply because the changelog has the name at the bottom.
> Tools/Scripts/webkitpy/xcode/simulator.py:287 > + return exit_code
Are there ever cases where we would need to clean up anything before returning here, or would a non-zero exit code always mean that it did not start anything?
> Tools/Scripts/webkitpy/xcode/simulator.py:298 > + return Simulator._boot_and_shutdown_simulator_device(host, udid) == 0 # Can boot device
Before you used not exit_code, here you use == 0. I think this should be consistent.
Daniel Bates
Comment 3
2015-02-17 14:18:48 PST
Comment on
attachment 246759
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=246759&action=review
>> Tools/Scripts/webkitpy/xcode/simulator.py:287 >> + return exit_code > > Are there ever cases where we would need to clean up anything before returning here, or would a non-zero exit code always mean that it did not start anything?
A non-zero exit code means that we did not boot the simulator device.
>> Tools/Scripts/webkitpy/xcode/simulator.py:298 >> + return Simulator._boot_and_shutdown_simulator_device(host, udid) == 0 # Can boot device > > Before you used not exit_code, here you use == 0. I think this should be consistent.
Will use not directive instead of equality testing.
Daniel Bates
Comment 4
2015-02-17 14:27:38 PST
Comment on
attachment 246759
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=246759&action=review
>>> Tools/Scripts/webkitpy/xcode/simulator.py:298 >>> + return Simulator._boot_and_shutdown_simulator_device(host, udid) == 0 # Can boot device >> >> Before you used not exit_code, here you use == 0. I think this should be consistent. > > Will use not directive instead of equality testing.
Actually, will land as-is. Notice that this function returns a boolean result and Simulator._boot_and_shutdown_simulator_device() returns an integer. We could write this line as: return not bool(Simulator._boot_and_shutdown_simulator_device(host, udid)) But this seems less clear than: return Simulator._boot_and_shutdown_simulator_device(host, udid) == 0
Daniel Bates
Comment 5
2015-02-17 14:30:15 PST
Comment on
attachment 246759
[details]
Patch Clearing flags on attachment: 246759 Committed
r180239
: <
http://trac.webkit.org/changeset/180239
>
Daniel Bates
Comment 6
2015-02-17 14:30:19 PST
All reviewed patches have been landed. Closing bug.
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