Bug 216847 - REGRESSION (r267421): [Catalina] TestWebKitAPI.WebKit.AccessibilityHasNoPreferencesServiceAccessWhenPostingNotification is failing
Summary: REGRESSION (r267421): [Catalina] TestWebKitAPI.WebKit.AccessibilityHasNoPrefe...
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-09-22 14:10 PDT by Ryan Haddad
Modified: 2020-09-22 20:50 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Haddad 2020-09-22 14:10:08 PDT 
The following test is consistently failing on Catalina bots:

    TestWebKitAPI.WebKit.AccessibilityHasNoPreferencesServiceAccessWhenPostingNotification
        
        /Volumes/Data/slave/catalina-release/build/Tools/TestWebKitAPI/Tests/WebKit/EnableAccessibility.mm:96
        Value of: !sandboxAccess()
          Actual: false
        Expected: true

https://results.webkit.org/?suite=api-tests&test=TestWebKitAPI.WebKit.AccessibilityHasNoPreferencesServiceAccessWhenPostingNotification

This appears to have started with https://trac.webkit.org/changeset/267421/webkit
Comment 1 Radar WebKit Bug Importer 2020-09-22 14:10:43 PDT 
<rdar://problem/69391096>
Comment 2 Truitt Savell 2020-09-22 16:59:30 PDT 
I am able to reproduce this test on r267421 by simply running it in iterations. I also confirmed it does not fail on r267418 which is the closest available spade to bisect with.
Comment 3 Per Arne Vollan 2020-09-22 17:43:52 PDT 
The changes in https://trac.webkit.org/r267421 should only be adding sandbox logging, so I am not yet able to understand why this test broke, but continuing to investigate.
Comment 4 Ryan Haddad 2020-09-22 20:50:54 PDT 
Moving this to resolved since the change was reverted in https://trac.webkit.org/changeset/267455 and the original bug was reopened.