| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
This test depends on some low-level features of the CPU and the OS
scheduler which seem impractical to automatically verify
independently of the test. So turn it off to stop its intermittent
failures in our test farm.
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Allow more variance for the benchlibtickcounter selftest.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cherry-pick of 548da9a5434d615456a7a6efda3380b7138c6000 and some
earlier changes predating public repo.
Note that this test is not failing if using Qt 4.5 only.
However, it fails if using Qt 4.5 selftests against Qt master testlib.
We want to be able to use master testlib to run 4.5 testcases,
and this change does no harm when using Qt 4.5 testlib, so backport
it to 4.5 for convenience.
Original change description follows:
A few tests use printf, which means they interfere with the XML test
logging. Blacklist them for the XML test.
Note that these tests happened to pass under the old test logger
implementation. That was because the test logger always printed XML
tags on a single line, and the printf calls contained no special XML
characters. The test logs generated were technically valid XML but
contained extraneous text.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The testlib subtests are conceptually not standalone unit tests, rather
they are helper programs for the real unit test, tst_selftests.
So, as is done for other similar tests (e.g. qprocess), don't name them
with `tst_'.
This makes it easier for automated tools to figure out that they
shouldn't directly run these tests.
Reviewed-by: Shane Bradley
|
| |
|
|
| |
perforce.
|
| |
|
