Skip to content
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

testsuite: add test for double-booking #1044

Merged
merged 1 commit into from
Jul 8, 2023

Conversation

garlick
Copy link
Member

@garlick garlick commented Jul 5, 2023

Problem: there is no test script for ensuring fluxion never allocates the same resources to multiple jobs.

Add a sharness script that utilizes the alloc-check plugin to account for allocated resources and catch errors. At this point, it just includes an "expected failure" test for #1043.

Note that this PR requires a version of flux-core with flux-framework/flux-core#5304 (just merged). I wanted to get this posted as I saw that @milroy was looking into #1043.

@garlick
Copy link
Member Author

garlick commented Jul 5, 2023

The fedora34 builder apparently did not reproduce the issue - I'm guessing maybe the timing is a little tight:

XPASS: t1024-alloc-check.t 7 - no jobs received alloc-check exception # TODO known breakage vanished

@garlick
Copy link
Member Author

garlick commented Jul 5, 2023

Well the 2s epilog I thought I had included was actually not enabled - fixed that.
Also fixed some issues with fluxion module loading/unloading and tidied a few things up.

garlick added a commit to garlick/flux-core that referenced this pull request Jul 5, 2023
Problem: alloc-check test was simplified when it was submitted
as flux-framework/flux-sched#1044.

Simplify script in a similar way.

For sched-simple, reduce the number of jobs submitted from 5 to 3
to expedite testing.
garlick added a commit to garlick/flux-core that referenced this pull request Jul 7, 2023
Problem: alloc-check test was simplified when it was submitted
as flux-framework/flux-sched#1044.

Simplify script in a similar way.

For sched-simple, reduce the number of jobs submitted from 5 to 3
to expedite testing.
Problem: there is no test script for ensuring fluxion never
allocates the same resources to multiple jobs.

Add a sharness script that utilizes the alloc-check plugin to
account for allocated resources and catch errors.  At this point,
it just includes an "expected failure" test for flux-framework#1043.
@garlick
Copy link
Member Author

garlick commented Jul 7, 2023

Test commits squashed, and a "skip" added for older flux-core as discused in ☕ time today.

@codecov
Copy link

codecov bot commented Jul 7, 2023

Codecov Report

Merging #1044 (f473791) into master (65da8f2) will increase coverage by 0.0%.
The diff coverage is n/a.

❗ Current head f473791 differs from pull request most recent head 615e943. Consider uploading reports for the commit 615e943 to get more accurate results

@@          Coverage Diff           @@
##           master   #1044   +/-   ##
======================================
  Coverage    74.3%   74.4%           
======================================
  Files          86      86           
  Lines        9432    9432           
======================================
+ Hits         7017    7020    +3     
+ Misses       2415    2412    -3     

see 1 file with indirect coverage changes

Copy link
Contributor

@grondo grondo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested this and LGTM. The exit: Invalid number: error seems to be a sharness bug (exit is being called with an empty arg, i.e. exit ""), though why it only manifests here is a mystery to me. Doesn't seem too important for now.

@garlick
Copy link
Member Author

garlick commented Jul 8, 2023

Thanks! I'll set MWP.

@garlick garlick added the merge-when-passing mergify.io - merge PR automatically once CI passes label Jul 8, 2023
@mergify mergify bot merged commit 1f76564 into flux-framework:master Jul 8, 2023
17 checks passed
milroy added a commit to milroy/flux-sched that referenced this pull request Jul 10, 2023
Problem: flux-framework#1044 introduced
tests to check for allocation failures due to jobs that
exceed their time limit. PR flux-framework#1044 had to define the two
`alloc-check` tests as `test_expect_failure` because the
mechanism to prevent multiple booking was not in place.

Update the two `alloc-check` tests to test_expect_success
since the PR of this commit fixes multiple booking in
Fluxion.
milroy added a commit to milroy/flux-sched that referenced this pull request Jul 11, 2023
Problem: flux-framework#1044 introduced
tests to check for allocation failures due to jobs that
exceed their time limit. PR flux-framework#1044 had to define the two
`alloc-check` tests as `test_expect_failure` because the
mechanism to prevent multiple booking was not in place.

Update the two `alloc-check` tests to test_expect_success
since the PR of this commit fixes multiple booking in
Fluxion.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
merge-when-passing mergify.io - merge PR automatically once CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants