
[unittest] Add lit option to allow disabling sharding in unittest By default, googletest based unit tests uses sharding to speed up the testing. However, when these unit tests are run through wrapper program on a remote platform with large round trip time, the sharding will increase the time cost dramatically. This patch adds a LLVM LIT option "--disable-gtest-sharding" to allow sharding on gtest based unittest to be disabled.
44 lines
1.4 KiB
Python
44 lines
1.4 KiB
Python
# Check the various features of the GoogleTest format.
|
|
|
|
# RUN: not %{lit} -v --disable-gtest-sharding --order=random %{inputs}/googletest-no-sharding > %t.out
|
|
# FIXME: Temporarily dump test output so we can debug failing tests on
|
|
# buildbots.
|
|
# RUN: cat %t.out
|
|
# RUN: FileCheck < %t.out %s
|
|
#
|
|
# END.
|
|
|
|
# CHECK: -- Testing:
|
|
# CHECK: FAIL: googletest-no-sharding :: [[PATH:[Dd]ummy[Ss]ub[Dd]ir/]][[FILE:OneTest\.py]]
|
|
# CHECK: *** TEST 'googletest-no-sharding :: [[PATH]][[FILE]]' FAILED ***
|
|
# CHECK-NEXT: Script(shard):
|
|
# CHECK-NEXT: --
|
|
# CHECK-NEXT: GTEST_OUTPUT=json:{{[^[:space:]]*}} GTEST_SHUFFLE=1 GTEST_RANDOM_SEED=123 {{.*}}[[FILE]]
|
|
# CHECK-NEXT: --
|
|
# CHECK-EMPTY:
|
|
# CHECK-NEXT: Script:
|
|
# CHECK-NEXT: --
|
|
# CHECK-NEXT: [[FILE]] --gtest_filter=FirstTest.subTestB
|
|
# CHECK-NEXT: --
|
|
# CHECK-NEXT: I am subTest B output
|
|
# CHECK-EMPTY:
|
|
# CHECK-NEXT: I am subTest B, I FAIL
|
|
# CHECK-NEXT: And I have two lines of output
|
|
# CHECK-EMPTY:
|
|
# CHECK: Script:
|
|
# CHECK-NEXT: --
|
|
# CHECK-NEXT: [[FILE]] --gtest_filter=FirstTest.subTestD
|
|
# CHECK-NEXT: --
|
|
# CHECK-NEXT: unresolved test result
|
|
# CHECK: ***
|
|
# CHECK: ***
|
|
# CHECK: Unresolved Tests (1):
|
|
# CHECK-NEXT: googletest-no-sharding :: FirstTest/subTestD
|
|
# CHECK: ***
|
|
# CHECK-NEXT: Failed Tests (1):
|
|
# CHECK-NEXT: googletest-no-sharding :: FirstTest/subTestB
|
|
# CHECK: Skipped{{ *}}: 1
|
|
# CHECK: Passed{{ *}}: 3
|
|
# CHECK: Unresolved{{ *}}: 1
|
|
# CHECK: Failed{{ *}}: 1
|