[all-commits] [llvm/llvm-project] 7de7fe: [lldb] Don't ask for QOS_CLASS_UNSPECIFIED queue i...
Raphael Isemann via All-commits
all-commits at lists.llvm.org
Tue Aug 25 11:14:20 PDT 2020
Branch: refs/heads/master
Home: https://github.com/llvm/llvm-project
Commit: 7de7fe5d0e3f7f4d28e1dde42df4a7defa564f11
https://github.com/llvm/llvm-project/commit/7de7fe5d0e3f7f4d28e1dde42df4a7defa564f11
Author: Raphael Isemann <teemperor at gmail.com>
Date: 2020-08-25 (Tue, 25 Aug 2020)
Changed paths:
M lldb/test/API/macosx/queues/TestQueues.py
M lldb/test/API/macosx/queues/main.c
Log Message:
-----------
[lldb] Don't ask for QOS_CLASS_UNSPECIFIED queue in TestQueues
TestQueues is curiously failing for me as my queue for QOS_CLASS_UNSPECIFIED
is named "Utility" and not "User Initiated" or "Default". While debugging, this
I noticed that this test isn't actually using this API right from what I understand. The API documentation
for `dispatch_get_global_queue` specifies for the parameter: "You may specify the value
QOS_CLASS_USER_INTERACTIVE, QOS_CLASS_USER_INITIATED, QOS_CLASS_UTILITY, or QOS_CLASS_BACKGROUND."
QOS_CLASS_UNSPECIFIED isn't listed as one of the supported values. swift-corelibs-libdispatch
even checks for this value and returns a DISPATCH_BAD_INPUT. The
libdispatch shipped on macOS seems to also check for QOS_CLASS_UNSPECIFIED and seems to
instead cause a "client crash", but somehow this doesn't trigger in this test and instead we just
get whatever queue
This patch just removes that part of the test as it appears the code is just incorrect.
Reviewed By: jasonmolenda
Differential Revision: https://reviews.llvm.org/D86211
More information about the All-commits
mailing list