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

[24.0] Record missing outputs as test errors #17874

Merged

Commits on Apr 2, 2024

  1. adapt output filter test

    - remove the output that is always present
    - add a test that has no outputs
    bernt-matthias committed Apr 2, 2024
    Configuration menu
    Copy the full SHA
    6687cdc View commit details
    Browse the repository at this point in the history
  2. tool verification: move no output assertion

    from planemo the verify_tool function is called from
    [within an try-except block](https://github.com/galaxyproject/planemo/blob/1aa3eb05a97ad20c0be6f6560ab5cec090e76612/planemo/engine/galaxy.py#L109)
    which silently catches any exception.
    
    Thus any exception raised from within verify_tool will not be
    detected, i.e. the assertion needs to be moved into
    `_verify_outputs` (which also seems to make sense by name)
    in order to make verify_tool record the problem properly.
    bernt-matthias committed Apr 2, 2024
    Configuration menu
    Copy the full SHA
    f19f4ae View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    46abd27 View commit details
    Browse the repository at this point in the history
  4. register failure to produce output

    thereby we implicitly make the assumption that a test needs to produce
    an output
    
    also make message more specific
    bernt-matthias committed Apr 2, 2024
    Configuration menu
    Copy the full SHA
    6da8719 View commit details
    Browse the repository at this point in the history
  5. register later

    bernt-matthias committed Apr 2, 2024
    Configuration menu
    Copy the full SHA
    fb01590 View commit details
    Browse the repository at this point in the history
  6. move assertion instead of removing it

    otherwise the tool test will just return a list out of bounds exception
    which is unclear to the user
    bernt-matthias committed Apr 2, 2024
    Configuration menu
    Copy the full SHA
    b05bfc3 View commit details
    Browse the repository at this point in the history
  7. Just use the suggestion

    Co-authored-by: Marius van den Beek <m.vandenbeek@gmail.com>
    bernt-matthias and mvdbeek committed Apr 2, 2024
    Configuration menu
    Copy the full SHA
    0b082d2 View commit details
    Browse the repository at this point in the history
  8. Configuration menu
    Copy the full SHA
    e0fee40 View commit details
    Browse the repository at this point in the history
  9. Add back test output

    bernt-matthias committed Apr 2, 2024
    Configuration menu
    Copy the full SHA
    ae594c1 View commit details
    Browse the repository at this point in the history
  10. Configuration menu
    Copy the full SHA
    e1ec2c8 View commit details
    Browse the repository at this point in the history
  11. move registering the exception

    then it might be clearer what's going on here
    bernt-matthias committed Apr 2, 2024
    Configuration menu
    Copy the full SHA
    1a545ae View commit details
    Browse the repository at this point in the history
  12. black

    bernt-matthias committed Apr 2, 2024
    Configuration menu
    Copy the full SHA
    8612c35 View commit details
    Browse the repository at this point in the history