Does not add job to history when re-running failed job

[habbes]

I noticed the following weird behaviour:

• Run a benchmark with errors, job starts running and added to history sidebar
• Job fails
• Fix code errors and re-run job
• The new job starts running but does not get added to job history, so if you click to a different job, you can't retrace the running job
• When you reload the browser, neither the new job or the failed job appear in the history

The expected behaviour is that whenever you run a job, it should appear in the history regardless of what the previous job was. Also, when you reload the browser, all the jobs should appear unless explicitly removed by the user.

[habbes]

In another attempt, after browser, the failed and new jobs appear in the history. The new job appears as queued even though it contains full logs to completion.

[habbes]

In another attempt, the issue occurred even when the job had not failed. It just seems like editing the current job's code and re-running causes some buggy behaviour.