You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing captive core with verify-range in AWS batch I encountered a few problems which made the experience unpleasant:
Manually editing the Job Definitions/Queues/Compute environments in the AWS console was hairy and error-prone.
Spawning jobs suffers from (1) aggravated by the need to calculate the ledger ranges (we have a spreadsheet for that, but still)
When a job fails, there is no way to simply respawn jobs. You need to manually create a new job by copy-pasting the fields of the failed job (increasing the number of retries is often not enough).
To improve the situation, I propose the following:
Spawn test jobs semi-automatically through CI (specify the base branch, click a button and have CI spawn the jobs). For GitHub Actions we could use https://www.actionspanel.app/ (I don't know if there is an equivalent solution for CircleCI)
CI could monitor jobs for failures and respawn them when the job failure is transient. We could also have a manual CI action which clones a job given its identifier.
The text was updated successfully, but these errors were encountered:
While testing captive core with verify-range in AWS batch I encountered a few problems which made the experience unpleasant:
To improve the situation, I propose the following:
The text was updated successfully, but these errors were encountered: