[swift-dev] linux long tests failing due to JUnit issue?

Jordan Rose jordan_rose at apple.com
Mon Aug 8 15:14:15 CDT 2016

> On Aug 6, 2016, at 15:15, Dave Abrahams via swift-dev <swift-dev at swift.org> wrote:
> I don't really understand why JUnit would be relevant here, but we're
> getting this failure after everything else seems to pass.
> [xUnit] [INFO] - Processing JUnit
> [xUnit] [INFO] - [JUnit] - No test report file(s) were found with the pattern 'Ninja-ReleaseAssert/swift-linux-x86_64/swift-test-results/x86_64-unknown-linux-gnu/lit-tests.xml' relative to '/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-14_04-long-test' for the testing framework 'JUnit'.  Did you enter a pattern relative to the correct directory?  Did you generate the result report(s) for 'JUnit'?
> [xUnit] [ERROR] - No test reports found for the metric 'JUnit' with the resolved pattern 'Ninja-ReleaseAssert/swift-linux-x86_64/swift-test-results/x86_64-unknown-linux-gnu/lit-tests.xml'. Configuration error?.
> [xUnit] [INFO] - Failing BUILD.
> See the bottom of:
> https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-14_04-long-test/lastBuild/consoleFull

For the record, Mishal says this is due to us changing the “subdir” option on the build configuration. I don’t think he’s gotten to updating the bot yet.


More information about the swift-dev mailing list