The latest job sent to each of my rigs has completed in almost exactly 3 hours.

Both jobs have names of the form :-

6v1nm_jp_TCRB_-2_front_-3_end_23_49374532_4mers_0001_0001_extract_B_SAVE_ALL_OUT_

My options are set to default run time.

Is it particularly these jobs or has the default run time been changed?

Or is it just coincidence?

It doesn’t look like the default has changed, since those TCRB tasks still come with the command-line option

-cpu_run_time 28800

But some batches of work do seem to do their own thing, and finish much earlier (or later) than the normal target run time.

It doesn’t look like the default has changed, since those TCRB tasks still come with the command-line option

-cpu_run_time 28800

But some batches of work do seem to do their own thing, and finish much earlier (or later) than the normal target run time.

Must be, all the other jobs appear to be running for 8 hours as normal.

I’ve had one sebvN_jp_TCRB task take over 11 hours to finish, and I’ve got three others still running after more than 10 (against a default run time of 8)

I’ve had one sebvN_jp_TCRB task take over 11 hours to finish, and I’ve got three others still running after more than 10 (against a default run time of 8)

I have most of my crunchers set to 36 hour tasks. I've had a couple of the Sebv ones roll through that you mentioned. Even though I have my WU's set to 36 hours, the Sebv ones are all ending early (about ~24hours in). They only produce 3 decoys in that time.