-
Notifications
You must be signed in to change notification settings - Fork 2
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
gitlab: add sched #15
Conversation
What failed:
|
Since the ^^ above is a hwloc issue and not a sched issue we're going to ignore the valgrind test in our CI for now. |
b3c240d
to
63d9f90
Compare
Dropped WIP. This is ready for a review. |
Whoops accidentally had two |
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.
LGTM! One suggestion inline, but feel free to ignore it if the current solution is working fine.
.gitlab-ci.yml
Outdated
- git clone https://github.com/flux-framework/flux-sched | ||
- cd flux-sched | ||
- module load gcc | ||
- ${CORE_INSTALL_PREFIX}/bin/flux start ./configure |
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.
I meant to mention that you could probably drop the start
here and just use /path/to/flux ./configure
. This is because when an explicit path is used with flux(1)
it will execute its argument with the same environment as would have been passed to a subcommand.
Try that and see if it works if you'd like.
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.
Oh, that's handy, thanks! Fixed and pushed.
I also noticed that the commit message was out of date. Fixed on recent push.
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.
LGTM!
Problem: We need to be testing flux-sched's integration with the rest of the framework, and we're not. Do that on corona and tioga since they're the system-instance clusters. Note that due to missing RPATH entries for certain libraries in Cray's compilers, this currently needs to be compiled with GCC. Also, the Valgrind test is temporarily exempted because it fails due to a memory leak in hwloc.
This is being put up as WIP because there are some failures in the testsuite when run under the gitlab runners:
Notably, the valgrind test is failing, even when I rerun it. I don't really see what the "missing test plan" is all about...