Note that I don't think we'll actually block a 1.16 release on fixing it. It *is* important for our ongoing development work, but as it is a test-suite issue not a user-facing issue it isn't a release blocker.
Note that I don't think we'll actually block a 1.16 release on fixing it. It *is* important for our ongoing development work, but as it is a test-suite issue not a user-facing issue it isn't a release blocker.