jsc failures after flux-core changes

[garlick]

After flux-framework/flux-core#1389 was merged, a bunch of sched sharness tests began failing.

Here is the sharness output for flux-sched beginning with the first failure, ending with the last failure.

Sched has PR #298 applied (0be7518) and flux-core was backed up to right after flux-framework/flux-core#1389 was applied: flux-framework/flux-core@bccf233

FAIL: t0002-waitjob.t 2 - waitjob: works when the job has not started
FAIL: t0002-waitjob.t 3 - waitjob: works when the job has already completed
FAIL: t0002-waitjob.t 4 - waitjob: works when the job started but has not completed
PASS: t0002-waitjob.t 5 - waitjob: remove sched module
ERROR: t0002-waitjob.t - exited with status 1
SKIP: t0003-basic-install.t - FLUX_SCHED_TEST_INSTALLED not set, skipping...
PASS: t0004-rdltool.t 1 - flux-rdltool exists
PASS: t0004-rdltool.t 2 - flux-rdltool resource works
PASS: t0004-rdltool.t 3 - flux-rdltool tree works
PASS: t0004-rdltool.t 4 - flux-rdltool aggregate works
PASS: t0004-rdltool.t 5 - flux-rdltool list-hierarchies works
FAIL: t1000-jsc.t 1 - jsc: expected job-event sequence for single-job scheduling
FAIL: t1000-jsc.t 2 - jsc: expected job-event sequence for multiple-job scheduling
FAIL: t1000-jsc.t 3 - jsc: expected single-job-event sequence in hwloc reader mode
FAIL: t1000-jsc.t 4 - jsc: expected multi-job-event sequence in hwloc reader mode
ERROR: t1000-jsc.t - exited with status 1
FAIL: t1001-rs2rank-basic.t 1 - rs2rank: multiple ranks manage a node in a shared fashion
FAIL: t1001-rs2rank-basic.t 2 - rs2rank: each manages an exclusive set of cores of a node
FAIL: t1001-rs2rank-basic.t 3 - rs2rank: each manages a node exclusively
FAIL: t1001-rs2rank-basic.t 4 - rs2rank: works with an inconsistent RDL (fewer cores)
FAIL: t1001-rs2rank-basic.t 5 - rs2rank: works with an inconsistent RDL (fewer nodes)
FAIL: t1001-rs2rank-basic.t 6 - rs2rank: works with a matched RDL
ERROR: t1001-rs2rank-basic.t - exited with status 1
SKIP: t1002-rs2rank-64ranks.t - LONGTEST not set, skipping...
SKIP: t1003-stress.t - LONGTEST not set, skipping...
PASS: t1004-module-load.t 1 - module-load: sched loads the fcfs plugin
FAIL: t1004-module-load.t 2 - module-load: submit and verify jobs to the fcfs plugin
PASS: t1004-module-load.t 3 - module-load: submit extra jobs to the fcfs plugin
PASS: t1004-module-load.t 4 - module-load: sched unloads the fcfs plugin
PASS: t1004-module-load.t 5 - module-load: sched loads the backfill plugin
PASS: t1004-module-load.t 6 - module-load: sched unloads the backfill plugin
PASS: t1004-module-load.t 7 - module-load: loads backfill with an argument meant for sched
PASS: t1004-module-load.t 8 - module-load: loads backfill with too deep reservation
PASS: t1004-module-load.t 9 - module-load: loads with slightly invalid reservation depth
PASS: t1004-module-load.t 10 - module-load: sched loads the backfill plugin with arguments
PASS: t1004-module-load.t 11 - module-load: no jobs are lost
ERROR: t1004-module-load.t - exited with status 1
FAIL: t1005-sched-params.t 1 - sched-params: works with a short queue depth (4)
FAIL: t1005-sched-params.t 2 - sched-params: works with queue-depth=16
FAIL: t1005-sched-params.t 3 - sched-params: works with a long queue depth (2048)
FAIL: t1005-sched-params.t 4 - sched-params: works with delay-sched=true
FAIL: t1005-sched-params.t 5 - sched-params: works with delay-sched=false
FAIL: t1005-sched-params.t 6 - sched-params: delay can be combined with a short depth
FAIL: t1005-sched-params.t 7 - sched-params: no-delay combines with a long depth
ERROR: t1005-sched-params.t - exited with status 1
FAIL: t1006-cancel.t 1 - cancel: cancelling a pending job works
PASS: t1006-cancel.t 2 - cancel: attempt to cancel nonexistent jobs must fail
FAIL: t1006-cancel.t 3 - cancel: attempt to cancel completed jobs must fail
ERROR: t1006-cancel.t - exited with status 1
PASS: t2000-fcfs.t 1 - sim: started successfully
FAIL: t2000-fcfs.t 2 - sim: scheduled and ran all jobs
PASS: t2000-fcfs.t 3 - jobs scheduled in correct order
ERROR: t2000-fcfs.t - exited with status 1
PASS: t2001-fcfs-aware.t 1 - sim: started successfully
FAIL: t2001-fcfs-aware.t 2 - sim: scheduled and ran all jobs
PASS: t2001-fcfs-aware.t 3 - jobs scheduled in correct order
ERROR: t2001-fcfs-aware.t - exited with status 1
PASS: t2002-easy.t 1 - sim: started successfully
FAIL: t2002-easy.t 2 - sim: scheduled and ran all jobs
FAIL: t2002-easy.t 3 - jobs scheduled in correct order
ERROR: t2002-easy.t - exited with status 1
PASS: t2003-fcfs-inorder.t 1 - sim: started successfully with queue-depth=1
FAIL: t2003-fcfs-inorder.t 2 - sim: scheduled and ran all jobs with queue-depth=1

[dongahn]

@garlick: did you apply flux-sched PR #295?

[garlick]

Nope I was confused. Closing.