You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's try adding moab scheduler integration with buildtest. This would require a couple of changes to codebase.
Suggest potential solution
We need a top-level executor declaration named moab in buildtest configuration file something like. This will define an executor name my_queue that is mapped to queue name dev.
. We need a new method to verify moab queues are up and running from ones specified in configuration file. For instance if queue dev is not enabled, we should make the executor invalid
Additional Information
No response
Post question in Slack
I agree that I posted my question in slack before creating this issue
Is there an existing issue
I confirm there is no existing issue for this issue
The text was updated successfully, but these errors were encountered:
Please describe your feature
Let's try adding moab scheduler integration with buildtest. This would require a couple of changes to codebase.
Suggest potential solution
moab
in buildtest configuration file something like. This will define an executor namemy_queue
that is mapped to queue namedev
.We need to update the json schema in https://github.com/buildtesters/buildtest/blob/devel/buildtest/schemas/settings.schema.json
msub
in the buildspec to do a simple job submission test such as sleep exampleThis will require updates to the following
buildtest/buildtest/builders/base.py
Lines 772 to 805 in 8c4e188
moab.py
with classMoabExecutor
andMoabJob
.buildtest/buildtest/config.py
Lines 168 to 180 in 8c4e188
dev
is not enabled, we should make the executor invalidAdditional Information
No response
Post question in Slack
Is there an existing issue
The text was updated successfully, but these errors were encountered: