| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Of late the test which fires up the window server, which has already
been the source of undue quantities of inconvenience, has taken to
hanging indefinitely when I run the test suite on a remote machine. Rope
at end, goodbye test, no review.
|
| |
|
|
|
|
|
| |
Re-enabling the disabled signature test along with changes which allow
it to pass. Closes #4238 again, no review. (But would anyone like to
expand the signature tests? Great idea, extempore!)
|
| | |
|
| |
|
|
|
| |
according to my tests, they all currently work.
|
| |
|
|
|
|
|
|
|
| |
of time because it fails if you can't connect to the screen of the test
machine. And then if any test fails, the stability test doesn't run. We
badly a separate testing area for tests which are prone to failure for
reasons which are unrelated to the quality ostensibly being tested. No
review.
|
| |
|
|
|
|
|
|
| |
[no content change] Fixed all SVN properties: mimes, EOL, executable. Id
expansion is consistently enabled for Scala/Java/C# sources in 'src/'
and consistently disabled and removed from everywhere else: there should
not be any dead Id tags anymore.
|
| | |
|
| | |
|
| |
|
|
|
| |
Removed old scala tests from new Scala core module.
|
| |
|
