Tests are timing sensitive and flaky on busy machines

[sternenseemann]

Observed this likely because the build machine was rather busy:

Running 1 test suites...
Test suite test: RUNNING...
Tests
  paramtree: FAIL
    Test output was different from 'tests/paramtree.golden'. It was:
    paramtree
      1 Int #1
        False Bool/'a' Char
          1337 Int #2:   OK (0.01s)
          42 Int #2:     OK
        True Bool
          'a' Char
            1337 Int #2: OK
            42 Int #2:   OK
          'x' Char
            1337 Int #2: OK
            42 Int #2:   OK
          'y' Char
            1337 Int #2: OK
            42 Int #2:   OK
      2 Int #1
        False Bool/'a' Char
          1337 Int #2:   OK
          42 Int #2:     OK
        True Bool
          'a' Char
            1337 Int #2: OK
            42 Int #2:   OK
          'x' Char
            1337 Int #2: OK
            42 Int #2:   OK
          'y' Char
            1337 Int #2: OK
            42 Int #2:   OK
    
    All 16 tests passed

1 out of 1 tests failed (0.01s)
Test suite test: FAIL
Test suite logged to: dist/test/paramtree-0.1.1.1-test.log
0 of 1 test suites (0 of 1 test cases) passed.

[merijn]

This is the result of tasty reporting the time a test took (if and only if it's more than 0.01s to run) and there's no convenient way to disable that without patching tasty. The easiest fix would be to use something other than tasty to test the code, but I can't really be bothered to write the necessary "mock tasty" code for that,