Skip flaky test on Firefox#180941
Conversation
There was a problem hiding this comment.
Code Review
This pull request skips a flaky test on Firefox by using the skip parameter in the test definition. My review provides a suggestion to improve how the test is skipped by providing a reason string directly to the skip parameter, which will improve test reporting.
ditman
left a comment
There was a problem hiding this comment.
Can confirm this test flaked in my (unrelated) PR as well. Ship it! (The skip with a String explanation is a nifty trick! It could even link back to the issue!)
|
(PS: Needs |
|
autosubmit label was removed for flutter/flutter/180941, because - The status or check suite Linux linux_unopt has failed. Please fix the issues identified (or deflake) before re-applying this label. |
mdebbar
left a comment
There was a problem hiding this comment.
This is wild. Why would the outline suddenly become 3px?
Anyhow, skipping sounds good to me.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
autosubmit label was removed for flutter/flutter/180941, because - The status or check suite Linux linux_host_engine has failed. Please fix the issues identified (or deflake) before re-applying this label. |
|
autosubmit label was removed for flutter/flutter/180941, because - The status or check suite Mac mac_ios_engine has failed. Please fix the issues identified (or deflake) before re-applying this label.
|
|
autosubmit label was removed for flutter/flutter/180941, because - The status or check suite Windows tool_integration_tests_2_9 has failed. Please fix the issues identified (or deflake) before re-applying this label. |
Skips flaky test on Firefox until #180940 is fixed.
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.