RESOLVED INVALID 243083
REGRESSION(r292107): [ iOS ] http/tests/paymentrequest/updateWith-shippingOptions.https.html is a constant text failure
https://bugs.webkit.org/show_bug.cgi?id=243083
Summary REGRESSION(r292107): [ iOS ] http/tests/paymentrequest/updateWith-shippingOpt...
Dawn Morningstar
Reported 2022-07-21 16:18:56 PDT
This is a continuation of https://bugs.webkit.org/show_bug.cgi?id=238581 http/tests/paymentrequest/updateWith-shippingOptions.https.html is still flakily and constantly failing on iOS though it has been resolved on Mac. HISTORY: https://results.webkit.org/?suite=layout-tests&test=http%2Ftests%2Fpaymentrequest%2FupdateWith-shippingOptions.https.html DIFF: --- /Volumes/Data/worker/Apple-iOS-15-Simulator-Release-GPUProcess-WK2-Tests/build/layout-test-results/http/tests/paymentrequest/updateWith-shippingOptions.https-expected.txt +++ /Volumes/Data/worker/Apple-iOS-15-Simulator-Release-GPUProcess-WK2-Tests/build/layout-test-results/http/tests/paymentrequest/updateWith-shippingOptions.https-actual.txt @@ -1,4 +1,4 @@ PASS Calling `updateWith` with a new `shippingOptions` without `requestShipping` should not update any values. -PASS Calling `updateWith` with a new `shippingOptions` should not update any other values. +FAIL Calling `updateWith` with a new `shippingOptions` should not update any other values. assert_equals: shipping option 0 selected should change expected (boolean) false but got (undefined) undefined DIFF-URL: https://build.webkit.org/results/Apple-iOS-15-Simulator-Release-GPUProcess-WK2-Tests/252687@main%20(2615)/http/tests/paymentrequest/updateWith-shippingOptions.https-diff.txt
Attachments
Radar WebKit Bug Importer
Comment 1 2022-07-21 16:20:11 PDT
Alexey Proskuryakov
Comment 2 2022-07-21 18:59:56 PDT
Looks like the results matches macOS now. But unlike macOS which went from one FAIL to a different one, iOS went from PASS to FAIL.
Ryan Haddad
Comment 3 2022-07-25 15:37:20 PDT
The consistent failure reported above is due to a misconfigured bot. There is nothing to fix in code here.
Note You need to log in before you can comment on or make changes to this bug.