DM-1223 Fixing start&stop timestamp persistance
Created by: rerpha
Description of work
From V20 test outcome - Fixing the persistence of previous job start and stop timestamps causing the filewriter to stop writing a new job suddenly.
This is a workaround, however I think a change in architecture should be made for CommandHandler
- See DM-1237
Also, ignore the crazy high additions number, its just a command in json to make sure it doesn't finish writing before the system test asserts that the job is still running.
Issue
Closes DM-1223
Acceptance Criteria
Added a reset when a new command is added Added system test to test that the stop timestamp from previous job is not applied to a new job.
Unit Tests
None modified
Other
None.
Code Review (To be filled in by the reviewer only)
-
Is the code of an acceptable quality? -
Do the changes function as described and is it robust?
Nominate for Group Code Review (Anyone can nominate it)
Indicate if you think the code should be reviewed in a Thursday code review session.
-
Recommend for group code review
Also, nominate it on the code_review Slack channel (does someone want to automate this?).