Files
tasks/tools/testrunner/testdata/junit-timeout-output.xml
Stephan BehnkeandGitHub 56451ed648 Mark timed out tests (#7332)
## What changed?
<!-- Describe what has changed in this PR -->

Append `(timeout)` to test failure of timed out test.

## Why?
<!-- Tell your future self why have you made these changes -->

So they can be easily spotted in the JUnit test output.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

Adapted existing tests.

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
2025-02-12 16:22:36 -08:00

10 lines
445 B
XML

<testsuites>
<testsuite name="suite" tests="0" failures="0" errors="0" id="0" time="">
<testcase name="TestCallbacksSuite/TestWorkflowCallbacks_1 (timeout)" classname="">
<failure message="Timeout"></failure>
</testcase>
<testcase name="TestCallbacksSuite/TestWorkflowCallbacks_2 (timeout)" classname="">
<failure message="Timeout"></failure>
</testcase>
</testsuite>
</testsuites>