Thread blocked indefinitely in an STM transaction

[newhoggy]

trafficstars

The "SetGlobalMinimalSeverity" test fails with "thread blocked indefinitely in an STM transaction" on Windows when built with ghc-8.6.5 and ghc-8.10.2

See https://github.com/input-output-hk/iohk-monitoring-framework/pull/597/checks?check_run_id=1318822544

[newhoggy]

I was not able to reproduce locally, but out of multiple local runs, I did get this other failure:

  Testing Trace
    Unit tests
      forked traces:                                               FAIL (0.06s)
        test\Cardano\BM\Test\Trace.lhs:492:
        Consecutive loggernames are not different: ["test.work1","test.work1","test.work0","test.work0","test.work1","test.work0"]

[newhoggy]

I spotted this failure in CI:

    Unit tests
      forked traces:                                               FAIL (0.10s)
        test/Cardano/BM/Test/Trace.lhs:492:
        Consecutive loggernames are not different: ["test.work1","test.work1","test.work0","test.work0","test.work1","test.work0"]

See https://github.com/input-output-hk/iohk-monitoring-framework/pull/597/checks?check_run_id=1324590355

[newhoggy]

There are also concurrency issues in file access on Windows. On Windows, by default, multiple processes cannot open handles to the same file and open files cannot be deleted.

      private messages should not be logged into private files:    FAIL

        Exception: D:\a\_temp\private.log: DeleteFile "\\\\?\\D:\\a\\_temp\\private.log": permission denied (The process cannot access the file because it is being used by another process.)

also

      default_scribe_must_log:                                     FAIL

        Exception: out-test.txt: DeleteFile "\\\\?\\D:\\a\\iohk-monitoring-framework\\iohk-monitoring-framework\\iohk-monitoring\\out-test.txt": permission denied (The process cannot access the file because it is being used by another process.)

See https://github.com/input-output-hk/iohk-monitoring-framework/pull/597/checks?check_run_id=1324590371

[newhoggy]

I can confirm that this is still happening: https://github.com/input-output-hk/iohk-monitoring-framework/pull/611/checks?check_run_id=1476894301

[deepfire]

Yes, I've definitely seen it to happen as well -- several times and recently.