Closed jasperla closed 9 years ago
With #22 applied this is fixed:
[1/1] cd /usr/obj/ports/tmux-mem-cpu-load-3.2.0/build-amd64 && /usr/local/bin/ctest --force-new-ctest-process
Test project /usr/obj/ports/tmux-mem-cpu-load-3.2.0/build-amd64
Start 1: usage
1/8 Test #1: usage ............................ Passed 0.00 sec
Start 2: no_arguments
2/8 Test #2: no_arguments ..................... Passed 1.00 sec
Start 3: custom_interval
3/8 Test #3: custom_interval .................. Passed 3.00 sec
Start 4: no_cpu_graph
4/8 Test #4: no_cpu_graph ..................... Passed 1.00 sec
Start 5: colors
5/8 Test #5: colors ........................... Passed 1.00 sec
Start 6: invalid_status_interval
6/8 Test #6: invalid_status_interval .......... Passed 0.00 sec
Start 7: invalid_graph_lines
7/8 Test #7: invalid_graph_lines .............. Passed 0.00 sec
Start 8: old_option_specification
8/8 Test #8: old_option_specification ......... Passed 0.00 sec
100% tests passed, 0 tests failed out of 8
Total Test time (real) = 6.02 sec
When running the tests for an upcoming OpenBSD port I noticed that the
--colors
test fails:Backtrace:
This happens both with and without MALLOC_OPTIONS set to
S
. Note that even when run without--colors
the memory reporting is odd:1421/-390MB [ ]