[SOLVED] Problems getting jobs started on Colossus

Lately, the usage of Colossus has increased, and now usually every node is running jobs.  This triggered a problem in the queue system, which basically prevented projects not already having a running job to get their jobs started.

We have now developed a local fix to the queue system so that this no longer happens.  The patch was applied today, and seems to work well. This means that now all projects should be able to get jobs started.

The most user visible change is that if you use the command "pending" to view your project's pending jobs, the top jobs should now get an estimated start time (most of the time, at least).