Ensure that Page.getOperatorList handles Annotation parsing errors correctly (issue 15557, bug 1794351)
#15558
Conversation
…correctly (issue 15557) *Fixes a regression from PR 15246, sorry about that!* The return value of all `Annotation.getOperatorList` methods was changed in PR 15246, however I missed updating the error code-path in `Page.getOperatorList` which thus breaks all operatorList-parsing for pages with corrupt Annotations.
|
/botio test |
From: Bot.io (Linux m4)ReceivedCommand cmd_test from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.241.84.105:8877/d134a79a16d1e81/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_test from @Snuffleupagus received. Current queue size: 0 Live output at: http://54.193.163.58:8877/8d4a96ffa59c479/output.txt |
From: Bot.io (Linux m4)FailedFull output at http://54.241.84.105:8877/d134a79a16d1e81/output.txt Total script time: 25.33 mins
Image differences available at: http://54.241.84.105:8877/d134a79a16d1e81/reftest-analyzer.html#web=eq.log |
From: Bot.io (Windows)FailedFull output at http://54.193.163.58:8877/8d4a96ffa59c479/output.txt Total script time: 30.14 mins
|
marco-c
changed the title
Page.getOperatorList handles Annotation parsing errors correctly (issue 15557)Page.getOperatorList handles Annotation parsing errors correctly (issue 15557, bug 1794351)
|
/botio makeref |
From: Bot.io (Linux m4)ReceivedCommand cmd_makeref from @calixteman received. Current queue size: 0 Live output at: http://54.241.84.105:8877/510cd7237fa5bc8/output.txt |
From: Bot.io (Windows)ReceivedCommand cmd_makeref from @calixteman received. Current queue size: 1 Live output at: http://54.193.163.58:8877/76e849b8e99e923/output.txt |
From: Bot.io (Linux m4)SuccessFull output at http://54.241.84.105:8877/510cd7237fa5bc8/output.txt Total script time: 21.83 mins
|
From: Bot.io (Windows)SuccessFull output at http://54.193.163.58:8877/76e849b8e99e923/output.txt Total script time: 22.60 mins
|
Fixes a regression from PR #15246, sorry about that!
The return value of all
Annotation.getOperatorListmethods was changed in PR #15246, however I missed updating the error code-path inPage.getOperatorListwhich thus breaks all operatorList-parsing for pages with corrupt Annotations.