-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong duration time (sometimes) calculated #226
Comments
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
This should most likely be SHL(DWORD_TO_LWORD(CpuCounter.cpuCntHiDW), 32) |
The expected behaviour is documented here: So to answer your question:
|
Could reproduce it and solved it in the PR |
Re-opening issue as the test-duration is still not calculated correctly for TEST_ORDERED(). See more details here:
Keeping this open until this issue is fully resolved to remember to close this for TcUnit 1.3.1. |
Maybe just revert the feature. I am not using TcUnit with ordered tests and I don’t have an example to debug the issue, it’s kinda hard for me to fix this, also I feels like ages since I worked on this. For a long time I am even mocking everything that is time dependent out of my tests to have all of them finish in 1 cyclic |
Solved in #231. |
Describe the bug
Sometimes the duration/time is wrongly calculated. This happens completely randomly and I have not been able to see why or any patterns. See screenshot below.
To Reproduce
Run tests over and over again. Eventually it will show up.
Screenshots
Software versions
Current master of TcUnit.
XAE 3.1.4024.50.
TcXaeShell.
Run environment
Virtual machine.
@stefanbesler
The text was updated successfully, but these errors were encountered: