RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-11-25 12:12:47 +01:00
Code Issues Projects Releases Wiki Activity
a7bd77dff1
llvm-mirror/utils/lit/tests/shtest-format.py

180 lines
6.9 KiB
Python
Raw Normal View History

[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# Check the various features of the ShTest format.
[NFCI][lit] Unbreak more lit self-tests after D98179 All of these depend on the order of tests, so if one runs them twice, the tests within them will naturally be reordered using the previous run times, which breaks them.
2021-03-22 12:44:30 +01:00
# FIXME: this test depends on order of tests
# RUN: rm -f %{inputs}/shtest-format/.lit_test_times.txt
[lit] Move the shtest-xunit-output check lines into shtest-format These two tests are operating on the same test suite, which causes them to be racy about writing temporary files and can cause spurious failures. Merge them into one test to avoid the issue. llvm-svn: 337718
2018-07-23 20:08:36 +02:00
# RUN: rm -f %t.xml
# RUN: not %{lit} -j 1 -v %{inputs}/shtest-format --xunit-xml-output %t.xml > %t.out
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# RUN: FileCheck < %t.out %s
[lit] Move the shtest-xunit-output check lines into shtest-format These two tests are operating on the same test suite, which causes them to be racy about writing temporary files and can cause spurious failures. Merge them into one test to avoid the issue. llvm-svn: 337718
2018-07-23 20:08:36 +02:00
# RUN: FileCheck --check-prefix=XUNIT < %t.xml %s
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# END.
# CHECK: -- Testing:
# CHECK: FAIL: shtest-format :: external_shell/fail.txt
[lit] Ensure test output is converted to strings where possible. - This cleans up the text output of failing tests when run under PY3. llvm-svn: 188416
2013-08-15 00:21:01 +02:00
# CHECK-NEXT: *** TEST 'shtest-format :: external_shell/fail.txt' FAILED ***
# CHECK: Command Output (stdout):
# CHECK-NEXT: --
# CHECK-NEXT: line 1: failed test output on stdout
# CHECK-NEXT: line 2: failed test output on stdout
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# CHECK: Command Output (stderr):
[lit] Ensure test output is converted to strings where possible. - This cleans up the text output of failing tests when run under PY3. llvm-svn: 188416
2013-08-15 00:21:01 +02:00
# CHECK-NEXT: --
[lit][tests][AIX] Update expected form of diagnostic messages; use `not` to normalize non-zero exit values Summary: Various tests in the `lit` testing suite expect specific return codes and forms of diagnostic message from utility programs. As per POSIX.1-2017 XCU Section 1.4, Utility Description Defaults, "[the] format of diagnostic messages for most utilities is unspecified". The STDERR subsections of the `cat` and `wc` utilities merely indicate that "[the] standard error shall be used only for diagnostic messages". The corresponding EXIT STATUS subsections merely indicate, with regard to errors, an exit value of >0. The affected tests are updated to accept the applicable diagnostic message as produced by the utilities on AIX. The exit value is normalized using `not` as necessary. Reviewers: xingxue, sfertile, jasonliu Reviewed By: xingxue Subscribers: delcypher, jsji, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D60553 llvm-svn: 359690
2019-05-01 17:47:16 +02:00
# CHECK-NEXT: cat{{(\.exe)?}}: {{cannot open does-not-exist|does-not-exist: No such file or directory}}
[lit] Ensure test output is converted to strings where possible. - This cleans up the text output of failing tests when run under PY3. llvm-svn: 188416
2013-08-15 00:21:01 +02:00
# CHECK: --
# CHECK: FAIL: shtest-format :: external_shell/fail_with_bad_encoding.txt
# CHECK-NEXT: *** TEST 'shtest-format :: external_shell/fail_with_bad_encoding.txt' FAILED ***
# CHECK: Command Output (stdout):
# CHECK-NEXT: --
# CHECK-NEXT: a line with bad encoding:
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# CHECK: --
[lit] Remove ANSI control characters from xunit output Failing test output sometimes contains control characters like \x1b (e.g. if there was some -fcolor-diagnostics output) which are not allowed inside XML files. This causes problems with CI systems: for example, the Jenkins JUnit XML will throw an exception when ecountering those characters and similar problems also occur with GitLab CI. Reviewed By: yln, jdenny Differential Revision: https://reviews.llvm.org/D84233
2020-08-06 09:53:47 +02:00
# CHECK: FAIL: shtest-format :: external_shell/fail_with_control_chars.txt
# CHECK-NEXT: *** TEST 'shtest-format :: external_shell/fail_with_control_chars.txt' FAILED ***
# CHECK: Command Output (stdout):
# CHECK-NEXT: --
# CHECK-NEXT: a line with {{.*}}control characters{{.*}}.
# CHECK: --
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# CHECK: PASS: shtest-format :: external_shell/pass.txt
# CHECK: FAIL: shtest-format :: fail.txt
[lit] Ensure test output is converted to strings where possible. - This cleans up the text output of failing tests when run under PY3. llvm-svn: 188416
2013-08-15 00:21:01 +02:00
# CHECK-NEXT: *** TEST 'shtest-format :: fail.txt' FAILED ***
# CHECK-NEXT: Script:
# CHECK-NEXT: --
# CHECK-NEXT: printf "line 1
# CHECK-NEXT: false
# CHECK-NEXT: --
# CHECK-NEXT: Exit Code: 1
#
# CHECK: Command Output (stdout):
# CHECK-NEXT: --
[lit] Report line number for failed RUN command (Relands r333584, reverted in 333592.) When debugging test failures with -vv (or -v in the case of the internal shell), this makes it easier to locate the RUN line that failed. For example, clang's test/Driver/linux-ld.c has 892 total RUN lines, and clang's test/Driver/arm-cortex-cpus.c has 424 RUN lines after concatenation for line continuations. When reading the generated shell script, this also makes it easier to locate the RUN line that produced each command. To support reporting RUN line numbers in the case of the internal shell, this patch extends the internal shell to support the null command, ":", except pipelines are not supported. To support reporting RUN line numbers in the case of windows cmd.exe as the external shell, this patch extends -vv to set "echo on" instead of "echo off" in bat files. (Support for windows cmd.exe as a lit external shell will likely be dropped later, but I found out too late.) Reviewed By: delcypher, asmith, stella.stamenova, jmorse, lebedev.ri, rnk Differential Revision: https://reviews.llvm.org/D44598 llvm-svn: 333614
2018-05-31 02:55:32 +02:00
# CHECK-NEXT: $ ":" "RUN: at line 1"
[lit] Improve readability of failing scripts. - This only applies to scripts executed by the _internal_ shell script interpreter. - This patch reworks the log to look more like a shell transcript, and be less verbose (but in the interest of calling attention to the important parts). Here is an example of the new format, for commands with/without failures and with/without output: ``` $ true $ echo hi hi $ false note: command had no output on stdout or stderr error: command failed with exit status 1 ``` llvm-svn: 271610
2016-06-03 01:49:42 +02:00
# CHECK-NEXT: $ "printf"
# CHECK-NEXT: # command output:
[lit] Ensure test output is converted to strings where possible. - This cleans up the text output of failing tests when run under PY3. llvm-svn: 188416
2013-08-15 00:21:01 +02:00
# CHECK-NEXT: line 1: failed test output on stdout
# CHECK-NEXT: line 2: failed test output on stdout
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# CHECK: UNRESOLVED: shtest-format :: no-test-line.txt
# CHECK: PASS: shtest-format :: pass.txt
# CHECK: UNSUPPORTED: shtest-format :: requires-missing.txt
# CHECK: PASS: shtest-format :: requires-present.txt
Reinstate "r292904 - [lit] Allow boolean expressions in REQUIRES and XFAIL and UNSUPPORTED" This reverts the revert in r292942. llvm-svn: 293007
2017-01-25 03:26:03 +01:00
# CHECK: UNRESOLVED: shtest-format :: requires-star.txt
# CHECK: UNSUPPORTED: shtest-format :: requires-triple.txt
# CHECK: PASS: shtest-format :: unsupported-expr-false.txt
# CHECK: UNSUPPORTED: shtest-format :: unsupported-expr-true.txt
# CHECK: UNRESOLVED: shtest-format :: unsupported-star.txt
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# CHECK: UNSUPPORTED: shtest-format :: unsupported_dir/some-test.txt
Reinstate "r292904 - [lit] Allow boolean expressions in REQUIRES and XFAIL and UNSUPPORTED" This reverts the revert in r292942. llvm-svn: 293007
2017-01-25 03:26:03 +01:00
# CHECK: PASS: shtest-format :: xfail-expr-false.txt
# CHECK: XFAIL: shtest-format :: xfail-expr-true.txt
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# CHECK: XFAIL: shtest-format :: xfail-feature.txt
# CHECK: XFAIL: shtest-format :: xfail-target.txt
# CHECK: XFAIL: shtest-format :: xfail.txt
# CHECK: XPASS: shtest-format :: xpass.txt
[lit] Lift XFAIL handling to core infrastructure. llvm-svn: 188949
2013-08-22 00:26:42 +02:00
# CHECK-NEXT: *** TEST 'shtest-format :: xpass.txt' FAILED ***
# CHECK-NEXT: Script
# CHECK-NEXT: --
# CHECK-NEXT: true
# CHECK-NEXT: --
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
[lit] Remove ANSI control characters from xunit output Failing test output sometimes contains control characters like \x1b (e.g. if there was some -fcolor-diagnostics output) which are not allowed inside XML files. This causes problems with CI systems: for example, the Jenkins JUnit XML will throw an exception when ecountering those characters and similar problems also occur with GitLab CI. Reviewed By: yln, jdenny Differential Revision: https://reviews.llvm.org/D84233
2020-08-06 09:53:47 +02:00
# CHECK: Failed Tests (4)
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# CHECK: shtest-format :: external_shell/fail.txt
[lit] Ensure test output is converted to strings where possible. - This cleans up the text output of failing tests when run under PY3. llvm-svn: 188416
2013-08-15 00:21:01 +02:00
# CHECK: shtest-format :: external_shell/fail_with_bad_encoding.txt
[lit] Remove ANSI control characters from xunit output Failing test output sometimes contains control characters like \x1b (e.g. if there was some -fcolor-diagnostics output) which are not allowed inside XML files. This causes problems with CI systems: for example, the Jenkins JUnit XML will throw an exception when ecountering those characters and similar problems also occur with GitLab CI. Reviewed By: yln, jdenny Differential Revision: https://reviews.llvm.org/D84233
2020-08-06 09:53:47 +02:00
# CHECK: shtest-format :: external_shell/fail_with_control_chars.txt
[lit] Add a test for the various ShTest format features. llvm-svn: 174072
2013-01-31 19:05:01 +01:00
# CHECK: shtest-format :: fail.txt
[lit] Improve naming of test result categories Improve consistency when printing test results: Previously we were using different labels for group names (the header for the list of, e.g., failing tests) and summary count lines. For example, "Failing Tests"/"Unexpected Failures". This commit changes lit to label things consistently. Improve wording of labels: When talking about individual test results, the first word in "Unexpected Failures", "Expected Passes", and "Individual Timeouts" is superfluous. Some labels contain the word "Tests" and some don't. Let's simplify the names. Before: ``` Failing Tests (1): ... Expected Passes : 3 Unexpected Failures: 1 ``` After: ``` Failed Tests (1): ... Passed: 3 Failed: 1 ``` Reviewed By: ldionne Differential Revision: https://reviews.llvm.org/D77708
2020-04-08 07:48:39 +02:00
# CHECK: Unexpectedly Passed Tests (1)
[lit] Improve consistency when printing test results
2019-02-28 06:46:04 +01:00
# CHECK: shtest-format :: xpass.txt
# CHECK: Testing Time:
[lit] Improve naming of test result categories Improve consistency when printing test results: Previously we were using different labels for group names (the header for the list of, e.g., failing tests) and summary count lines. For example, "Failing Tests"/"Unexpected Failures". This commit changes lit to label things consistently. Improve wording of labels: When talking about individual test results, the first word in "Unexpected Failures", "Expected Passes", and "Individual Timeouts" is superfluous. Some labels contain the word "Tests" and some don't. Let's simplify the names. Before: ``` Failing Tests (1): ... Expected Passes : 3 Unexpected Failures: 1 ``` After: ``` Failed Tests (1): ... Passed: 3 Failed: 1 ``` Reviewed By: ldionne Differential Revision: https://reviews.llvm.org/D77708
2020-04-08 07:48:39 +02:00
# CHECK: Unsupported : 4
[AIX] Split lit test shtest-format into two separate tests and add AIX as UNSUPPORTED for shtest-format-argv0 Summary: lit test `shtest-format.py` fails on AIX because one of the subtest of shtest-format requires the tool `[` to be installed under the system PATH. For AIX, `[` is only available as a shell builtin and does not present as an executable file under PATH. Hence, split the original shtest-format into two separate test files and added AIX as UNSUPPORTED for the test using `[` . Reviewers: daltenty, hubert.reinterpretcast Reviewed By: hubert.reinterpretcast Subscribers: delcypher, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D82100
2020-06-18 22:51:53 +02:00
# CHECK: Passed : 6
[lit] Improve naming of test result categories Improve consistency when printing test results: Previously we were using different labels for group names (the header for the list of, e.g., failing tests) and summary count lines. For example, "Failing Tests"/"Unexpected Failures". This commit changes lit to label things consistently. Improve wording of labels: When talking about individual test results, the first word in "Unexpected Failures", "Expected Passes", and "Individual Timeouts" is superfluous. Some labels contain the word "Tests" and some don't. Let's simplify the names. Before: ``` Failing Tests (1): ... Expected Passes : 3 Unexpected Failures: 1 ``` After: ``` Failed Tests (1): ... Passed: 3 Failed: 1 ``` Reviewed By: ldionne Differential Revision: https://reviews.llvm.org/D77708
2020-04-08 07:48:39 +02:00
# CHECK: Expectedly Failed : 4
# CHECK: Unresolved : 3
[lit] Remove ANSI control characters from xunit output Failing test output sometimes contains control characters like \x1b (e.g. if there was some -fcolor-diagnostics output) which are not allowed inside XML files. This causes problems with CI systems: for example, the Jenkins JUnit XML will throw an exception when ecountering those characters and similar problems also occur with GitLab CI. Reviewed By: yln, jdenny Differential Revision: https://reviews.llvm.org/D84233
2020-08-06 09:53:47 +02:00
# CHECK: Failed : 4
[lit] Improve naming of test result categories Improve consistency when printing test results: Previously we were using different labels for group names (the header for the list of, e.g., failing tests) and summary count lines. For example, "Failing Tests"/"Unexpected Failures". This commit changes lit to label things consistently. Improve wording of labels: When talking about individual test results, the first word in "Unexpected Failures", "Expected Passes", and "Individual Timeouts" is superfluous. Some labels contain the word "Tests" and some don't. Let's simplify the names. Before: ``` Failing Tests (1): ... Expected Passes : 3 Unexpected Failures: 1 ``` After: ``` Failed Tests (1): ... Passed: 3 Failed: 1 ``` Reviewed By: ldionne Differential Revision: https://reviews.llvm.org/D77708
2020-04-08 07:48:39 +02:00
# CHECK: Unexpectedly Passed: 1
[lit] Move the shtest-xunit-output check lines into shtest-format These two tests are operating on the same test suite, which causes them to be racy about writing temporary files and can cause spurious failures. Merge them into one test to avoid the issue. llvm-svn: 337718
2018-07-23 20:08:36 +02:00
[lit] Small refinements for xunit report output
2020-05-02 00:20:18 +02:00
# XUNIT: <?xml version="1.0" encoding="UTF-8"?>
[lit] Include total elapsed time in xunit output The time= attribute can also be used for the testsuites tag. While this attribute appears to be ignored by Jenkins (https://github.com/jenkinsci/junit-plugin/blob/bab34bcc96154a494f8c371953efe06d45813f67/src/main/java/hudson/tasks/junit/SuiteResult.java#L202), it is still useful if you manually inspect the xml file. Reviewed By: yln Differential Revision: https://reviews.llvm.org/D84230
2020-07-23 11:45:55 +02:00
# XUNIT-NEXT: <testsuites time="{{[0-9.]+}}">
[lit] Remove ANSI control characters from xunit output Failing test output sometimes contains control characters like \x1b (e.g. if there was some -fcolor-diagnostics output) which are not allowed inside XML files. This causes problems with CI systems: for example, the Jenkins JUnit XML will throw an exception when ecountering those characters and similar problems also occur with GitLab CI. Reviewed By: yln, jdenny Differential Revision: https://reviews.llvm.org/D84233
2020-08-06 09:53:47 +02:00
# XUNIT-NEXT: <testsuite name="shtest-format" tests="22" failures="8" skipped="4">
[lit] Move the shtest-xunit-output check lines into shtest-format These two tests are operating on the same test suite, which causes them to be racy about writing temporary files and can cause spurious failures. Merge them into one test to avoid the issue. llvm-svn: 337718
2018-07-23 20:08:36 +02:00
# XUNIT: <testcase classname="shtest-format.external_shell" name="fail.txt" time="{{[0-9]+\.[0-9]+}}">
# XUNIT-NEXT: <failure{{[ ]*}}>
# XUNIT: </failure>
# XUNIT-NEXT: </testcase>
# XUNIT: <testcase classname="shtest-format.external_shell" name="fail_with_bad_encoding.txt" time="{{[0-9]+\.[0-9]+}}">
# XUNIT-NEXT: <failure{{[ ]*}}>
# XUNIT: </failure>
# XUNIT-NEXT: </testcase>
[lit] Remove ANSI control characters from xunit output Failing test output sometimes contains control characters like \x1b (e.g. if there was some -fcolor-diagnostics output) which are not allowed inside XML files. This causes problems with CI systems: for example, the Jenkins JUnit XML will throw an exception when ecountering those characters and similar problems also occur with GitLab CI. Reviewed By: yln, jdenny Differential Revision: https://reviews.llvm.org/D84233
2020-08-06 09:53:47 +02:00
# XUNIT: <testcase classname="shtest-format.external_shell" name="fail_with_control_chars.txt" time="{{[0-9]+\.[0-9]+}}">
# XUNIT-NEXT: <failure><![CDATA[Script:
# XUNIT: Command Output (stdout):
# XUNIT-NEXT: --
# XUNIT-NEXT: a line with [2;30;41mcontrol characters[0m.
# XUNIT: </failure>
# XUNIT-NEXT: </testcase>
[lit] Move the shtest-xunit-output check lines into shtest-format These two tests are operating on the same test suite, which causes them to be racy about writing temporary files and can cause spurious failures. Merge them into one test to avoid the issue. llvm-svn: 337718
2018-07-23 20:08:36 +02:00
# XUNIT: <testcase classname="shtest-format.external_shell" name="pass.txt" time="{{[0-9]+\.[0-9]+}}"/>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="fail.txt" time="{{[0-9]+\.[0-9]+}}">
# XUNIT-NEXT: <failure{{[ ]*}}>
# XUNIT: </failure>
# XUNIT-NEXT: </testcase>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="no-test-line.txt" time="{{[0-9]+\.[0-9]+}}">
# XUNIT-NEXT: <failure{{[ ]*}}>
# XUNIT: </failure>
# XUNIT-NEXT: </testcase>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="pass.txt" time="{{[0-9]+\.[0-9]+}}"/>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="requires-missing.txt" time="{{[0-9]+\.[0-9]+}}">
[lit] Small refinements for xunit report output
2020-05-02 00:20:18 +02:00
# XUNIT-NEXT:<skipped message="Missing required feature(s): a-missing-feature"/>
[lit] Move the shtest-xunit-output check lines into shtest-format These two tests are operating on the same test suite, which causes them to be racy about writing temporary files and can cause spurious failures. Merge them into one test to avoid the issue. llvm-svn: 337718
2018-07-23 20:08:36 +02:00
# XUNIT: <testcase classname="shtest-format.shtest-format" name="requires-present.txt" time="{{[0-9]+\.[0-9]+}}"/>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="requires-star.txt" time="{{[0-9]+\.[0-9]+}}">
# XUNIT-NEXT: <failure{{[ ]*}}>
# XUNIT: </failure>
# XUNIT-NEXT: </testcase>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="requires-triple.txt" time="{{[0-9]+\.[0-9]+}}">
[lit] Small refinements for xunit report output
2020-05-02 00:20:18 +02:00
# XUNIT-NEXT:<skipped message="Missing required feature(s): x86_64"/>
[lit] Move the shtest-xunit-output check lines into shtest-format These two tests are operating on the same test suite, which causes them to be racy about writing temporary files and can cause spurious failures. Merge them into one test to avoid the issue. llvm-svn: 337718
2018-07-23 20:08:36 +02:00
# XUNIT: <testcase classname="shtest-format.shtest-format" name="unsupported-expr-false.txt" time="{{[0-9]+\.[0-9]+}}"/>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="unsupported-expr-true.txt" time="{{[0-9]+\.[0-9]+}}">
[lit] Include unexecuted tests in xUnit report Pass in all discovered tests to report generators. The XunitReport generator now creates testcase items for unexecuted tests and documents why they have been skipped. This makes it easier to compare test runs with different filters or configurations, or across platforms. I don't know who is using the JsonReport generator and what the expectations there are (it doesn't have tests), so decided to preserve the old behavior by filtering out the unexecuted tests. Reviewed By: jdenny Differential Revision: https://reviews.llvm.org/D81316
2020-06-06 00:45:43 +02:00
# XUNIT-NEXT:<skipped message="Unsupported configuration"/>
[lit] Move the shtest-xunit-output check lines into shtest-format These two tests are operating on the same test suite, which causes them to be racy about writing temporary files and can cause spurious failures. Merge them into one test to avoid the issue. llvm-svn: 337718
2018-07-23 20:08:36 +02:00
# XUNIT: <testcase classname="shtest-format.shtest-format" name="unsupported-star.txt" time="{{[0-9]+\.[0-9]+}}">
# XUNIT-NEXT: <failure{{[ ]*}}>
# XUNIT: </failure>
# XUNIT-NEXT: </testcase>
# XUNIT: <testcase classname="shtest-format.unsupported_dir" name="some-test.txt" time="{{[0-9]+\.[0-9]+}}">
[lit] Include unexecuted tests in xUnit report Pass in all discovered tests to report generators. The XunitReport generator now creates testcase items for unexecuted tests and documents why they have been skipped. This makes it easier to compare test runs with different filters or configurations, or across platforms. I don't know who is using the JsonReport generator and what the expectations there are (it doesn't have tests), so decided to preserve the old behavior by filtering out the unexecuted tests. Reviewed By: jdenny Differential Revision: https://reviews.llvm.org/D81316
2020-06-06 00:45:43 +02:00
# XUNIT-NEXT:<skipped message="Unsupported configuration"/>
[lit] Move the shtest-xunit-output check lines into shtest-format These two tests are operating on the same test suite, which causes them to be racy about writing temporary files and can cause spurious failures. Merge them into one test to avoid the issue. llvm-svn: 337718
2018-07-23 20:08:36 +02:00
# XUNIT: <testcase classname="shtest-format.shtest-format" name="xfail-expr-false.txt" time="{{[0-9]+\.[0-9]+}}"/>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="xfail-expr-true.txt" time="{{[0-9]+\.[0-9]+}}"/>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="xfail-feature.txt" time="{{[0-9]+\.[0-9]+}}"/>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="xfail-target.txt" time="{{[0-9]+\.[0-9]+}}"/>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="xfail.txt" time="{{[0-9]+\.[0-9]+}}"/>
# XUNIT: <testcase classname="shtest-format.shtest-format" name="xpass.txt" time="{{[0-9]+\.[0-9]+}}">
# XUNIT-NEXT: <failure{{[ ]*}}>
# XUNIT: </failure>
# XUNIT-NEXT: </testcase>
# XUNIT: </testsuite>
# XUNIT-NEXT: </testsuites>
Reference in New Issue Copy Permalink