-
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
Duration is not calculated when running tests in sequence #210
Comments
@stefanbesler I just merged your changes in. Unfortunately, not everything works. See above. Could you look into it? |
Initial fix done. Needs to be tested more. See #211 for the details. |
Hm, not sure what went wrong here. What’s left to do, where can I help? |
Hey! I ran all the timed/sequence examples to verify everything is fine now and it looks good. I've realized it's a little annoying to run these manually to verify that the functionality is OK. Will have to think of a way to automate this. |
Describe the bug
Whenever running tests in sequence (any of the examples here, the duration is always calculated to be 0.0.
To Reproduce
Clone the latest master, run any of the examples above, and see the duration be 0.0.
Expected behavior
Duration should be correctly calculated, just like in the case when running tests that are not in sequence (so running in parallell).
Screenshots
Software versions
TwinCAT 3.1.4024.44.
Visual Studio 2019 (according to the contributing guidelines).
TcUnit from master.
Run environment
Running in virtual machine.
Additional context
Note that build-chain for TcUnit has been updated. Please look at Contributing markdown file.
The text was updated successfully, but these errors were encountered: