- Aug 17, 2020
-
-
Martin Christoph Hierholzer authored
-
- Aug 11, 2020
-
-
Martin Killenberg authored
- Also removed race conditions in the test.
-
- Aug 10, 2020
- Aug 07, 2020
- Aug 06, 2020
-
-
vargheseg authored
- runtimeErrorHandling_testPushTypeReadNonBlocking
-
- Aug 05, 2020
- Aug 03, 2020
-
-
vargheseg authored
-
- Jul 31, 2020
- Jul 24, 2020
-
-
vargheseg authored
fixture_with_poll_and_push_input exposes pollVariable, pushVariable as refernce types for convenience.
-
- Jul 22, 2020
- Jul 15, 2020
- Jul 14, 2020
-
-
Martin Killenberg authored
-
vargheseg authored
The fixture in testExceptionHandling.cc created the ChimeraTK::TestFacility before the ChimeraTK::Application. This is unspported. The TestFacility implicity requries an Application instance already existing before being initialized. Changing the oder of member declaration solved the exception being thrown from the fixture.
-
Martin Killenberg authored
-
- Jul 13, 2020
-
-
Martin Killenberg authored
-
- Jul 09, 2020
- Apr 20, 2020
-
-
Martin Killenberg authored
-
- Apr 14, 2020
-
-
Martin Christoph Hierholzer authored
Initially, devices are closed and hence there is an error message. It goes away shortly when the device got opened. The new behavior is according to specification.
-
Martin Christoph Hierholzer authored
allows to control whether to wait for device recoveries in stepApplication
-
- Mar 05, 2020
-
-
Martin Christoph Hierholzer authored
-
- Feb 27, 2020
-
-
Zenker, Dr. Klaus (FWKE) - 126506 authored
This is not correlated to the new feature implemented in this branch. It was needed to compile this version.
-
vargheseg authored
Fix changes broken by renaming to ExceptionDummyBackend in DeviceAccess.
-
- Feb 26, 2020
-
-
vargheseg authored
-
- Feb 04, 2020
-
-
Martin Christoph Hierholzer authored
need to wait until all mainLoops() are entered, so the initial value propagation is done. Otherwise during initial value propagation values could be read from hardware which might already trigger the exception state.
-
Martin Christoph Hierholzer authored
one initial value was not properly waited for, and one inherent race condition is now basically ignored (with comment)
-
- Jan 27, 2020
-
-
vargheseg authored
All variables from the cs to device have been initialized with a non zero default before the test starts.
-
- Jan 23, 2020
-
-
Martin Christoph Hierholzer authored
-
- Jan 22, 2020
-
-
Martin Killenberg authored
They return as soon as the condition is fulfilled, so there is no harm in having long timeouts in case the tests are successful. The only drawback is that it takes longer in case of errors.
-
- Jan 21, 2020
-
-
Martin Christoph Hierholzer authored
-
- Jan 20, 2020
-
-
Martin Christoph Hierholzer authored
-