Ticket 434

Summary:	New job array test
Product:	Slurm	Reporter:	Moe Jette <jette>
Component:	Test Suite	Assignee:	Nathan Yee <nyee32>
Status:	RESOLVED FIXED	QA Contact:
Severity:	5 - Enhancement
Priority:	---
Version:	14.03.x
Hardware:	Linux
OS:	Linux
Site:	SchedMD	Alineos Sites:	---
Atos/Eviden Sites:	---	Confidential Site:	---
Coreweave sites:	---	Cray Sites:	---
DS9 clusters:	---	HPCnow Sites:	---
HPE Sites:	---	IBM Sites:	---
NOAA SIte:	---	OCF Sites:	---
Recursion Pharma Sites:	---	SFW Sites:	---
SNIC sites:	---	Linux Distro:	---
Machine Name:		CLE Version:
Version Fixed:		Target Release:	---
DevPrio:	---	Emory-Cloud Sites:	---
Attachments:	Test28.6 test that the job arrays will run on multiple partitions Found errors in earlier patch, but this is test28.6 that test job arrays on mutliple partitions

Description Moe Jette 2013-09-30 07:17:56 MDT

We had some problems with job arrays being submitted to multiple partitions so I would like a test added for this functionality. You should be able to re-use some existing logic from test3.5 (create and delete new partition) and 28.1 (submit job array). Here is the sequence to test.

1. Create a new partition with the same nodes as the default partition
2. Submit job array to both the default partition and new partition
3. Verify the job array runs (two elements in the array is sufficient)
4. Delete the new partition

Comment 1 Nathan Yee 2013-10-12 08:23:08 MDT

Created attachment 445 [details]
Test28.6 test that the job arrays will run on multiple partitions

Comment 2 Nathan Yee 2013-10-13 09:08:50 MDT

Created attachment 448 [details]
Found errors in earlier patch, but this is test28.6 that test job arrays on mutliple partitions

Comment 3 Moe Jette 2013-10-14 07:56:05 MDT

Changes noted below already made:

Please remember to submit test jobs with a time limit so they get cleaned up in a timely fashion.
Please use tabs for indentation in both C and Expect.
I changed some logic to use the global functions.
What I really wanted tested is a single job submited to two partitions at the same time, it will run in one of them (e.g. sbatch --partition=foo,bar ...").