Get isar-robot to fail some tasks

[Eddasol]

Get isar-robot to fail some task such that testing through isar-robot will touch larger parts of the code and to allow for testing of failure behaviour.

One option is to use environment variables to decide if it should fail or not.

Some different types of isar-robot that could have different behaviour:

• PlaceBot (successfully completes every task after x seconds)
• NoceBot (regular missions always fails)
• LostBot (localization step always fails)
• SlowBot (spends 1 minute per task)
• InstantBot (spends no time per task)
• VagaBot (never returns home)
• OfflineBot (Shuts down mid mission)

Prerequisite

• Make isar-robot configurable #118

[andchiind]

This would be very useful for equinor/flotilla#894 and issue #871 in general

[Christdej]

Would it be an idea to have a mission with a specific ID or a certain step that will cause isar-robot to send and error back or mark mission as failed?

[Christdej]

Or make isar-robot configurable to always succeed or always fail, and run one of each instances in dev

[tsundvoll]

Will solve this using the Mission.name attribute to decide if a mission should fail some tasks, by reporting step.status = StepStatus.Failed

[tsundvoll]

Can this be tested with an integration test from ISAR?

[haakonsf]

Offline state to be introduced in https://github.com/orgs/equinor/projects/85/views/4?pane=issue&itemId=56783224

[aeshub]

This issue has automatically been marked as stale as there has been no activity for 60 days.