Wrong duration time (sometimes) calculated about tcunit

[sagatowski]

[stefanbesler]

Sorry, I am a bit busy at the moment, I can look into this somewhen next week.

Since this is so sporadic and the duration is off by such a large value, I think it has to do with this here

TcUnit/TcUnit/TcUnit/POUs/Functions/F_GetCpuCounterAs64bit.TcPOU

Line 14 in 4a48bdd

F_GetCpuCounterAs64bit := SHL(32, DWORD_TO_LWORD(CpuCounter.cpuCntHiDW)) + DWORD_TO_LWORD(CpuCounter.cpuCntLoDW);]]></ST>

This should most likely be

SHL(DWORD_TO_LWORD(CpuCounter.cpuCntHiDW), 32)

[TimSalzmann]

Can you give me a hint? I run TcUnit verifier 1.2.1.0 hand have 118 faild test is that correct? I want to simulate the random error.

[sagatowski]

@TimSalzmann

The expected behaviour is documented here:
https://github.com/tcunit/TcUnit/tree/master/TcUnit-Verifier

So to answer your question:

TcUnit/TcUnit-Verifier/TcUnit-Verifier_DotNet/TcUnit-Verifier/Program.cs

Line 21 in 4a48bdd

private static int expectedNumberOfFailedTests = 118; // Update this if you add intentionally failing tests

[stefanbesler]

Could reproduce it and solved it in the PR