1[DEFAULT]
2head = head.js
3support-files =
4  ../shared-head.js
5skip-if = toolkit == 'android' || socketprocess_networking
6
7[test_active_configuration.js]
8[test_start.js]
9skip-if = true
10[test_get_features.js]
11[test_responsiveness.js]
12skip-if = tsan # Times out on TSan, bug 1612707
13[test_shared_library.js]
14[test_run.js]
15skip-if = true
16[test_pause.js]
17[test_enterjit_osr.js]
18skip-if = (os == "win" && processor == "aarch64") # aarch64 due to 1536652
19[test_enterjit_osr_disabling.js]
20skip-if = !debug
21[test_enterjit_osr_enabling.js]
22skip-if = !debug
23[test_asm.js]
24[test_feature_mainthreadio.js]
25skip-if = release_or_beta || (os == "win" && processor == "aarch64") # The IOInterposer is in an ifdef, aarch64 due to 1536657
26
27# The sanitizer checks appears to overwrite our own memory hooks in xpcshell tests,
28# and no allocation markers are gathered. Skip this test in that configuration.
29[test_feature_nativeallocations.js]
30skip-if = asan || tsan
31
32# Native stackwalking is somewhat unreliable depending on the platform.
33#
34# We don't have frame pointers on macOS release and beta, so stack walking does not
35# work. See Bug 1571216 for more details.
36#
37# Linux can be very unreliable when native stackwalking through JavaScript code.
38# See Bug 1434402 for more details.
39#
40# For sanitizer builds, there were many intermittents, and we're not getting much
41# additional coverage there, so it's better to be a bit more reliable.
42[test_feature_stackwalking.js]
43skip-if = (os == "mac" && release_or_beta) || (os == "linux" && release_or_beta && !debug) || asan || tsan
44
45[test_feature_js.js]
46skip-if = tsan # Times out on TSan, bug 1612707
47
48# See the comment on test_feature_stackwalking.js
49[test_merged_stacks.js]
50skip-if = (os == "mac" && release_or_beta) || (os == "linux" && release_or_beta && !debug) || asan || tsan
51