| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
I am not happy with this solution; a better way is to use uniformly
unicode or bytes in both Pythons, but this seems too disruptive for now.
|
| |
|
|
|
|
| |
This allows ^C during test discovery
|
| |
|
| |
|
|
|
|
| |
Mostly done by manually checking 2to3 output
|
|
|
|
| |
Thanks to aspidites <emarshall85@gmail.com> who provided the patch.
|
|
|
|
|
| |
This reverts commit 9711f78f790d10d914e08851544c6fc96f9a030a, as it's
causing build phailures in phabricator.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
* Adjusts performance tests
* Change ghcpkg05.stderr-mingw32 to match ghcpkg05.stderr
Test Plan: Ran 'sh validate' and observed fewer test failures afterwards
Reviewers: austin
Reviewed By: austin
Differential Revision: https://phabricator.haskell.org/D191
|
|
|
|
| |
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
New function signal_exit_code hides differences between target platforms
handling of fatal error signals and the applications' exit codes. E.g.
on Linux the application exit code which receives fatal error signal
is encoded as 128 + signal value. On the other hand on Solaris
the application exit code is signal value alone.
Test Plan: validated on Linux and tested on Solaris
Reviewers: austin, simonmar
Reviewed By: simonmar
Subscribers: phaskell, simonmar, relrod, ezyang, carter
Differential Revision: https://phabricator.haskell.org/D122
|
| |
|
|
|
|
|
|
|
| |
With THREADS=n, for n > 1, it becomes impossible to match the
performance numbers to the test case name. Hence include it in the
output. This also makes grepping through a bunch of logs for a specific
test case much easier, and outweighs the extra verbosity.
|
|
|
|
|
| |
this makes it easier to spot a “just over the mark” change (e.g. +5.1%),
compared to a more radical jump (e.g. +15%).
|
|
|
|
|
| |
which makes it print performance numbers even when the test succeeds
(good for historic analysis)
|
|
|
|
| |
Signed-off-by: Austin Seipp <austin@well-typed.com>
|
|
|
|
|
|
|
|
|
|
|
| |
check_stdout(f) allows you to override the test framework's
diff based output checking with another mechanism. f is
a function which takes two arguments: the first is the
filename containing the observed stdout, the second is the
normaliser that would have been applied (in case you want
to read, normalise, and then do something.)
Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
|
|
|
|
| |
Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>
|
| |
|
|
|
|
| |
by ensuring this in the test runner.
|
|
|
|
|
|
| |
uname -s
msys gives "MINGW32"
msys2 gives "MINGW_NT-6.2"
|
|
|
|
|
|
| |
More often than not the output of the performance tests is in the way,
rather than helping. This allows the use of `make SKIP_PERF_TESTS=YES`
to skip these tests. Fixes #8413
|
| |
|
|
|
|
|
|
|
|
|
| |
Select verbosity with "make VERBOSE=n". Options so far:
n=0: No per-test output
n=1: Only failing test results
n=2: As above, plus progress information (names of all tests)
n=3: As aobve, plus commands called.
Default currently is n=3, although n=2 might be a nicer default.
|
| |
|
| |
|
|
|
|
|
| |
This makes the test run alone, to increase the chance of a
multi-CPU race happening.
|
| |
|
| |
|
|
|
|
| |
The driver now also supports nested lists of setup functions
|
|
|
|
| |
Predicates now match the order they are documented on the wiki
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The name 'os' clashes with a python library
|
|
|
|
|
|
| |
Gives a list of tickets that the testsuite thinks are broken, and
what bug it thinks is the reason. This can then be pasted into trac
and 'previewed', which will show any closed tickets with strikeout.
|
|
|
|
|
|
| |
In particular, the 3 values you most need to care about (framework
failures, unexpected passes, unexpected failures) are now together
in a block.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Uses look like
stats_num_field('bytes allocated',
[(wordsize(32), 45648, 5),
(wordsize(64), 49400, 5)])
where the first matching triple will be used. e.g. we could override
the Win32 expected values with:
[(platform('i386-unknown-mingw32'), 41000, 5),
(wordsize(32), 45648, 5),
(wordsize(64), 49400, 5)])
with other 32-bit platforms falling through to the wordsize(32) case.
This makes it easier to give different values for different platforms,
while being sure that all platforms are covered.
|
| |
|