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

[21.05] Don't start workflow scheduler for handler in job pool #12075

Merged
merged 1 commit into from
Jun 1, 2021

Conversation

mvdbeek
Copy link
Member

@mvdbeek mvdbeek commented May 30, 2021

Broken in #11792,
fixes #11986.

This only happens when the job handler is configured to attach to a job
pool. Includes a test that reproduces the issue.

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

Broken in galaxyproject#11792,
fixes galaxyproject#11986.

This only happens when the job handler is configured to attach to a job
pool. Includes a test that reproduces the issue.
@mvdbeek mvdbeek added kind/bug area/jobs area/configuration Galaxy's configuration system labels May 30, 2021
@mvdbeek mvdbeek added this to the 21.05 milestone May 30, 2021
@mvdbeek
Copy link
Member Author

mvdbeek commented May 30, 2021

The package test failure is unrelated, and may or may not be fixed by common-workflow-language/schema_salad#393

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/configuration Galaxy's configuration system area/jobs kind/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Job handlers acting as workflow schedulers despite presence of explicit workflow schedulers
2 participants