-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plugin: disable queue validation on an unknown queue, no configured "default" queue #281
Changes from all commits
2c568e2
1f2ddca
d51eca2
11f3c6b
c507a1e
8f560c3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -44,7 +44,7 @@ test_expect_success 'submit a job successfully under default bank' ' | |
jobid1=$(flux mini submit -n1 hostname) && | ||
flux job wait-event -f json $jobid1 priority | jq '.context.priority' > job1.test && | ||
cat <<-EOF >job1.expected && | ||
10050000 | ||
50000 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It might be useful to state in the commit message why the priority changes are a result of the changes in validating queues since, at least to me, that is not an obvious effect. Though please correct me if this should be clear. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, looking back I realize this isn't as obvious as I initially thought, sorry about that. The reason the priority changes for these jobs is because the queue factor is |
||
EOF | ||
test_cmp job1.expected job1.test | ||
' | ||
|
@@ -53,7 +53,7 @@ test_expect_success 'submit a job successfully under second bank' ' | |
jobid2=$(flux mini submit --setattr=system.bank=account2 -n1 hostname) && | ||
flux job wait-event -f json $jobid2 priority | jq '.context.priority' > job2.test && | ||
cat <<-EOF >job2.expected && | ||
10050000 | ||
50000 | ||
EOF | ||
test_cmp job2.expected job2.test | ||
' | ||
|
@@ -78,7 +78,7 @@ test_expect_success 'submit a job successfully under second bank' ' | |
jobid3=$(flux mini submit --setattr=system.bank=account2 -n1 hostname) && | ||
flux job wait-event -f json $jobid3 priority | jq '.context.priority' > job3.test && | ||
cat <<-EOF >job3.expected && | ||
10050000 | ||
50000 | ||
EOF | ||
test_cmp job3.expected job3.test | ||
' | ||
|
@@ -92,7 +92,7 @@ test_expect_success 'try to submit job under new default user/bank entry' ' | |
jobid4=$(flux mini submit -n1 hostname) && | ||
flux job wait-event -f json $jobid4 priority | jq '.context.priority' > job4.test && | ||
cat <<-EOF >job4.expected && | ||
10050000 | ||
50000 | ||
EOF | ||
test_cmp job4.expected job4.test | ||
' | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Commit message nit: The commit message says:
But it appears that here
INVALID_QUEUE
is still defined.Also:
I don't see a
UNSPECIFIED_QUEUE
, but there is aNO_QUEUE_SPECIFIED
...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops, I totally messed that up, didn't I? I meant to update this commit message before posting the PR but completely forgot. I'll update the commit message to use both
UNKNOWN_QUEUE
(instead ofINVALID_QUEUE
) andNO_QUEUE_SPECIFIED
(instead ofUNSPECIFIED_QUEUE
). Sorry for the confusion!There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While you are in there, it might be good to add comments on each of these #defines to say more of what each means. Not critical, but if you are modifying the commit anyway...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, good suggestion. I will do that!