I have still been seeing CI test failures; this should definitely fix that. It adds a taskPriority member to control the priority of event and user update tasks and elevates that priority from .background to .low. When running LyticsTests -- the ones that have been failing on the GitHub runner -- the default priority will be used. This change only affects top-level tasks and they all use the same priority so this should not present any issues in terms of priority inversion.
I have still been seeing CI test failures; this should definitely fix that. It adds a
taskPrioritymember to control the priority of event and user update tasks and elevates that priority from.backgroundto.low. When runningLyticsTests-- the ones that have been failing on the GitHub runner -- the default priority will be used. This change only affects top-level tasks and they all use the same priority so this should not present any issues in terms of priority inversion.