Closed Karl-G1 closed 2 years ago
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
What does this Pull Request accomplish?
Workaround for Issue #211
When the new tests are run individually, they pass. When run sequentially, LabVIEW RT / VeriStand engine is prone to crashing, which results in various errors.
I filed issue #211 from this failure, and this PR works around the issue for now:
Deploy with Reboot and Retry.vi
andReboot Active Target.vi
globalSetUp.vi
Why should this Pull Request be merged?
More fully test the ability for the custom device (and VeriStand) to support Combo cRIO targets.
What testing has been done?
Ran the tests against the ATS cRIO.