removes nextRuns in the past when job skipped by locker #828

[manuelarte]

What does this do?

It proposes a possible solution for the bug described in #828

Which issue(s) does this PR fix/relate to?

Resolves #828

List any changes that modify/break current functionality

no breaking of current functionality

Have you included tests for your changes?

Will include them after we agree on the solution

Did you document any new/modified functionality?

• Updated example_test.go
• Updated README.md

Notes

[manuelarte]

Some somments:

I added a new channel to "update" the nextScheduled array. In the current draft I decided to create a new channel and a new method to handle this update of the nextScheduled, but there are other places where the nextScheduled array is updated and I am not reusing code.

I decided to create a new channel, but maybe it makes sense to modify the method selectExecJobsOutForRescheduling and also "remove" the old entries in nextScheduled.

Or any other solution that I don't see right now.

What do you guys think?

[JohnRoesler]

hey @manuelarte

I considered a few options, and without changing any other behavior, this seems like a reasonable route to go. Thanks for digging in and putting forth a fix.