* Fixing VMSS Re-Image 7-Day Timer
* Updating use of TimeStamp to created_at
* Renaming.
* Updating field name.
* Removing test chagne.
* Updating query to work if init_at entry does not exist yet.
* Changing timer for testing.
* Adding field comment.
* Formatting models.py
* Fixing where save is called.
* Adidng logging.
* Removing logging. Ready for merge.
* Update src/pytypes/onefuzztypes/models.py
Co-authored-by: Joe Ranweiler <joe@lemma.co>
* Formatting.
* Updating datetime.
* Testing after datetime change.
* Removing test.
Co-authored-by: nharper285 <nharper285@gmail.com>
Co-authored-by: Joe Ranweiler <joe@lemma.co>
* only reimage nodes that are in the done state
* ignore done message when the node is deleted
* log warning instead of error when receiving a heartbeat from a deleted node
In practice, Application Insights can take up to 3 minutes before something sent to it is available via KQL.
This PR logs a start and stop marker such that the integration tests only search for logs during the integration tests. This reduces the complexity when using the integration tests during the development process.
Note: this migrated the new functionality from #356 into the latest integration test tools.
Enables co-locating multiple tasks in a given work-set.
Tasks are bucketed by the following:
* OS
* job id
* setup container
* VM SKU & image (used in pre-1.0 style tasks)
* pool name (used in 1.0+ style tasks)
* if the task needs rebooting after the task setup script executes.
Additionally, a task will end up in a unique bucket if any of the following are true:
* The task is set to run on more than one VM
* The task is missing the `task.config.colocate` flag (all tasks created prior to this functionality) or the value is False
This updates the libfuzzer template to make use of colocation. Users can specify co-locating all of the tasks *or* co-locating the secondary tasks.
