needs to be added to the list of exceptions `found_exceptions`
because otherwise it can't be controlled by `expect_test_failure`
therefore expect_num_outputs needs to be checked after the job run.
because the exceptions are added via `register_exception`
which needs job's stdio
follow up on https://github.com/galaxyproject/galaxy/pull/10304
These peptide IDs were previously parsed as floats. The result was that
peptides that were too large were rounded, and the ID was no longer
meaningful, resulting in the "PSM Detail for Selected Peptides" table
not being populated.
With this change PEPTIDE_ID field is no longer parsed as a float, and
remains a string.
This cannot be tested like this now, because instead of a real data property we relay on the emit event to modify the parents `value` prop.
The fact that we are using `v-model="currentValue"` in both inputs should guarantee that both inputs have the same value.
when loading macros from imported files
the base property of the node is
overwritten.
this adds a xml:base property to the node
which is printed in the test
their own means of setting a log file. Read the supervisor log if it
exists and the daemon log does not, since failure to start Galaxy will
prevent creation of the daemon log file.
When running first startup in CI, attempt to read log files from
multiple places to make debugging different types of failures possible.
this adds functionality to the linter functions to return the lint
context. without breaking previous behavior.
Planemo seems to use
- lint_tool_source (which returned the fail state) and
- lint_tool_source_with (which returned nothing)
For the later a parameter has been added to make the linter silent
and the lint context is now returned.
For the former a variant has been added which returns the lint context.
The .. and ... and ... and within a lambda gives you
no chance to debug the test without a print statement or
a debugger.
Co-authored-by: Marius van den Beek <m.vandenbeek@gmail.com>
mvdbeek