-
Notifications
You must be signed in to change notification settings - Fork 6k
Re-enable Fuchsia tests #18342
Re-enable Fuchsia tests #18342
Conversation
exit 0 | ||
# This is longer than the test timeout as dumping the | ||
# logs can sometimes take longer. | ||
ssh_timeout_seconds=360 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like in some cases the timeouts are happening after 2 mins. That may be a default timeout inside fuchsia_ctl we may need to take a look.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like you are already covering it with the logs collection timeout.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On glancing at the Fuchsia CTL code, the timeout passed here as an arg should override any default timeouts set. I kicked off a couple of runs to make sure that this does fix the issue. I'll keep an eye out for any potential failures.
9b67074
to
781a77b
Compare
here is the LUCI run: https://ci.chromium.org/swarming/task/4c278c3f83514a10?server=chromium-swarm.appspot.com |
testing/fuchsia/run_tests.sh
Outdated
--identity-file $pkey | ||
|
||
echo "$(date) START:REBOOT ------------------------------------------" | ||
# note: this will set an exit code of 255, which we can ignore. | ||
./fuchsia_ctl -d $device_name ssh -c "dm reboot-recovery" \ | ||
--timeout-seconds $ssh_timeout_seconds \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may want to use the default here, this operation should complete within milliseconds.
testing/fuchsia/run_tests.sh
Outdated
@@ -61,6 +64,7 @@ echo "$(date) START:WAIT_DEVICE_READY -------------------------------" | |||
for i in {1..10}; do | |||
./fuchsia_ctl -d $device_name ssh \ | |||
--identity-file $pkey \ | |||
--timeout-seconds $ssh_timeout_seconds \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here the operation should complete in ms, with a faulty device this will block for 60mins
781a77b
to
9f76f96
Compare
This reverts commit efdc099.
* 7b64067 Use 'message' as the parameter name in FlMessageCodec::encode_message (flutter/engine#18253) * 429beae Roll src/third_party/skia 3d2c41b773f6..3ebadcc98eab (14 commits) (flutter/engine#18333) * 66ba3a7 Roll src/third_party/dart 2bf325900586..d6fed1f62444 (1 commits) (flutter/engine#18334) * 2f8495a Completely disable paving the device on Fuchsia (flutter/engine#18340) * 006dbfc Always keep thread merged when there are platform views. (flutter/engine#18245) * 21b4d2f [web] Fix paragraph positioning (flutter/engine#18329) * efdc099 Re-enable Fuchsia tests (flutter/engine#18342) * ae2222f Revert "Re-enable Fuchsia tests (#18342)" (flutter/engine#18345)
Co-authored-by: Kaushik Iska <kaushikiska@google.com>
This reverts commit efdc099.
Per my analysis here, most of the failures seem to be test timeouts. I'm attempting to enable the tests again.