GitLab

queue is no longer needed for cleanup, and the docstrings should
reflect the changed behavior.

These are the test cases for the bug that precipitated this hunt.  These
should largely be degenerate with the other single-equivalence cases
(because they are now single-equivalence cases), but do things like
make sure that drains are getting correctly cleared and times are
getting correctly reset.

After discussions, the current find_queue_equivalence_classes for this
system really only complicates the codebase for very little actual gain.
After this, the system will have only one equivalence class at all times
consisting of all active queues assigned to nodes and all active
reservations.

This simplification allows us to ensure that find_job_location only gets
called twice, once for reservations, which ignore drain times, and then
immediately after for the normal "production" queue jobs, which do set
drain times.  In both cases we can just clear drain times across the
machine.

In addition to testing (and more tests coming for the case that caused
this examination to begin with), we know that this works, as any system
with a queue or set of overlapping queues across all resources on the
machine forms a single equivalence class under the old code.

Resolve "Fix ValueError not being raised in right place"

Closes #119

See merge request aig/cobalt!78

The value error was being raised if locations were being removed from
the queue as a part of a reservation and was not being handled correctly
for the case when you request locations outside of your defined queue.

ValueError is now being raised correctly.

Resolve "cqadm --run doesn't work for Cray systems"

Closes #117

See merge request aig/cobalt!75

updating specfiles to remove launcher from default client install and wrapper.

Closes #118

See merge request aig/cobalt!74

Resolve "Fix spacing in cdbwriter.py"

Closes #107

See merge request aig/cobalt!70

Forkers that have unregistered will no longer be used to start jobs.

Closes #101

See merge request aig/cobalt!67

Forward merge of changes from develop.

patch to fix out-of-spec Cray API call result.

Closes #102

See merge request !68

I don't even know how I missed this in preliminary testing.  The forker
increment is now fixed when using multiple forkers.  Additionally, the
first forker in the list was always getting used regardless of status,
which kind of defeats the entire point of this patch.

Resolve "Enh: Add abilitiy to request SSD nodes"

Closes #93

See merge request !66

Revert "Merge branch 'revert-fe04ae24' into 'develop'"

See merge request !65

This reverts merge request !62

Revert "Merge branch 'revert-cd19412c' into 'develop'"

See merge request !64