[macOS] Additional test scripts fail with: usage: mktemp [-d] [-q] [-t prefix] [-u] template ... mktemp [-d] [-q] [-u] -t prefix FAIL test_*.sh (exit status: 1) (all main tests pass))

[barracuda156]

After a fix to threads.h, I ran tests on 10.6 PowerPC. All main tests pass:

Available: no SIMD optimizations
In use: no SIMD optimizations

* Suite sad_tests:
.....................................................
53 tests - 53 pass, 0 fail, 0 skipped (1365 ticks, 0.001 sec)

* Suite intra_sad_tests:
..........
10 tests - 10 pass, 0 fail, 0 skipped (503 ticks, 0.001 sec)

* Suite satd_tests:
...............
15 tests - 15 pass, 0 fail, 0 skipped (772 ticks, 0.001 sec)

* Suite dct_tests:
..........
10 tests - 10 pass, 0 fail, 0 skipped (2979 ticks, 0.003 sec)

* Suite coeff_sum_tests:
.
1 tests - 1 pass, 0 fail, 0 skipped (45 ticks, 0.000 sec)

* Suite mv_cand_tests:
...
3 tests - 3 pass, 0 fail, 0 skipped (103 ticks, 0.000 sec)

Total: 92 tests (6433 ticks, 0.006 sec), 41073 assertions
Pass: 92, fail: 0, skip: 0.
PASS kvazaar_tests (exit status: 0)

However all extra tests fail, identically:

=========================================
   kvazaar 2.2.0: tests/test-suite.log
=========================================

# TOTAL: 14
# PASS:  2
# SKIP:  0
# XFAIL: 0
# FAIL:  12
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: test_gop.sh
=================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_gop.sh (exit status: 1)

FAIL: test_interlace.sh
=======================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_interlace.sh (exit status: 1)

FAIL: test_intra.sh
===================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_intra.sh (exit status: 1)

FAIL: test_invalid_input.sh
===========================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_invalid_input.sh (exit status: 1)

FAIL: test_mv_constraint.sh
===========================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_mv_constraint.sh (exit status: 1)

FAIL: test_owf_wpp_tiles.sh
===========================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_owf_wpp_tiles.sh (exit status: 1)

FAIL: test_rate_control.sh
==========================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_rate_control.sh (exit status: 1)

FAIL: test_slices.sh
====================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_slices.sh (exit status: 1)

FAIL: test_smp.sh
=================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_smp.sh (exit status: 1)

FAIL: test_tools.sh
===================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_tools.sh (exit status: 1)

FAIL: test_weird_shapes.sh
==========================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_weird_shapes.sh (exit status: 1)

FAIL: test_pu_depth_constraints.sh
==================================

usage: mktemp [-d] [-q] [-t prefix] [-u] template ...
       mktemp [-d] [-q] [-u] -t prefix 
FAIL test_pu_depth_constraints.sh (exit status: 1)

Looks like something is wrong with the set-up. Also, anything valgrind will not work on Darwin PowerPC, since valgrind is known to be broken there (it does not build and cannot therefore run anything).

[fador]

Thanks for testing it, but I think the main tests are enough on normal cases and the extra tests are mostly for our internal checking to see that the algorithms work as they should, there should not be platform specific bugs detected, or at least they typically are not 🤔

[barracuda156]

@fador I will run those on an Intel system just to see if it is arch-related or macOS version-related (or maybe our set-up related, after all).