| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
And so my attempt to have a performance test draws the final curtain, no
review.
|
|
|
|
|
| |
No review.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implementing foreach to work in parallel in ParIterableLike.
Doing a bunch of refactoring around in the collection framework to
ensure a parallel foreach is never called with a side-effecting method.
This still leaves other parts of the standard library and the compiler
unguarded.
No review.
|
|
|
|
|
|
|
| |
Oh the irony, disabling the failing test made the build fail, because
another test is hardcoded to use its paths. Disabled that test too.
We'll put humpty back together again. No review.
|
|
|
|
|
|
| |
We need a successful build, not sure why this hasn't been disabled yet.
Disabled failing coder test, no review.
|
|
|
|
|
| |
Disabled test not actually doing anything anyway, 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!)
|
|
|
|
|
|
|
| |
Reverting some recent signature code and temporarily disabling a test so
I can work this out without shattering the tranquility of the build. No
review.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
reinstate the disabled test.
COMMITTERS: the test is very fragile. If you don't run the whole test
suite (it's the very last one which runs!) then you broke the build.
Upon your toes you should be.
For anyone unaware, test/partest --update-check path/to/test will
magically pass any test and update the checkfile to resemble whatever
output it just produced. Incautious use of this feature may negatively
impact the mood of certain extempores.
No review.
|
|
|
|
|
|
|
|
|
|
| |
After seeing the 481 line diff I had to apply to bring the checkfile up
to date, I concluded this test cannot be in the general pool: this is
the third build break in the last few days, because it changes output
like some people change socks. (Hygenic people.) Sorry to move it to
disabled iulian, but I don't know what else to do with it on short
notice. Review by dragos.
|
| |
|
|
|
|
|
|
| |
Re-enabled test spec-traits (removed the swing dependent part, since all
it tested was call-by-name parameters). no review.
|
|
|
|
|
|
|
|
| |
Switched back to StoreReporter for presentation compiler tests. This
eats up error messages, but if the output is correct we don't mind a
spurious error here and there. Renabled simple presentation compiler
tests. no review.
|
|
|
|
|
|
| |
Updated completion tests, still waiting for a divergent implicits fix in
the presentation compiler. no review.
|
|
|
|
|
|
| |
Made the presentation compiler reporter in interactive tests show up
error messages.no review.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Disentangled scaladoc and the presentation compiler. Now there are
different flags, forInteractive and forScaladoc, instead of the
overloaded onlyPresentation. While it is unfortunate to have these
flags, I know of no easy way to customize the typer (the behavior they
control is pretty deep into the analyzer). This shaves off around 100MB
of unnecessary docComments from the presentation compiler. review by
odersky, dubochet.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Fixed a scalacheck test group "test entire subdirectory" problem. It's
now possible to add scalacheck tests consisting of multiple files. No
review.
|
|
|
|
|
|
|
| |
Temporarily disabled collections checks to keep build from breaking.
No review
|
|
|
|
|
|
| |
compile because the specialized variants of apply were not implemented
as well. Fixed by extending runtime.AbstractFunction0 instead.
|
|
|
|
|
| |
according to my tests, they all currently work.
|
| |
|
|
|
|
|
|
| |
I figured it'd be a miracle if I got the script test past our fickle
robot overseers. Disabled, no review.
|
|
|
|
|
|
|
|
| |
changes necessary to plug it back in while preserving everything which
has happened since then in tests and such, but we should be the lookout
for overreversion. Review by phaller (but as a formality, I don't think
it requires direct review.)
|
|
|
|
|
|
|
|
| |
Tightened what gets specialized: only when the type parameter appears
at top level, or as a type argument to a Java array. For example T,
Array[T] cause specialization, but List[T] does not. Resurrected
spec-matrix, forgotten among the disabled tests. No review.
|
|
|
|
|
|
|
| |
symbol does not cause any crashes, but the method using an unknown
symbol will not be used for inlining. Resurrected tests, removed
spec-matrix for the moment. No review.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Disabling what I think are the last two failing tests, one each of the
two leading bugs among those we've seen here today on testing theater:
"could not find toMap: (x$1: scala.collection.TraversableOnce,x$2:
Predef$<:<)"
and
"scala.tools.nsc.symtab.Types$TypeError: method react cannot be
accessed in java.lang.Object with scala.actors.Reactor[Any]
No review but hey lets' see if we can re-enable these tests soonish.
|
|
|
|
|
|
| |
Disabled test that hangs when actors package is compiled with
specialization. Review by dragos.
|
|
|
|
|
| |
Disabling some more tests which crash under -optimise. No review.
|
|
|
|
|
| |
Disabled the test which is hanging the -optimise run. No review.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If I work on this patch any longer without checking in I will go
stark raving mad. It is broken up into a couple pieces. This one is
the changes to test/. It includes fixing a bunch of tests, removing
deprecated constructs, moving jars used by tests to the most specific
plausible location rather than having all jars on the classpath of all
tests, and some filesystem layout change (continuations get their whole
own srcpath.) This would be the world's most tedious review, so let's
say no review.
[Note: after this commit, I doubt things will build very smoothly until
the rest of the partest changes follow. Which should only be seconds,
but just in case.]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While working on partest discovered that CompilerCommand ignores half
its constructor arguments and a couple dozen places blithely pass it
those arguments as if they're being used. Then there were setups like
this:
class OfflineCompilerCommand(
arguments: List[String],
settings: Settings,
error: String => Unit,
interactive: Boolean)
extends CompilerCommand(arguments, new Settings(error), error, false)
Hey offline compiler command, why throw away the perfectly good settings
you were given? Ever heard 'reduce, reuse, recycle'? How did you ever
work... or do you? No review.
|
|
|
|
|
|
| |
Temporarily disabling failing test until I can finish my partest work.
No review.
|
|
|
|
|
|
|
|
| |
what must be legacy scalatest.* properties to partest.*, boldly assuming
that the fact that partest is pretty much unusable outside of scalac
means there are no users outside of scalac who might be disrupted by
eliminating old property names. Review by community.
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
Moved some test cases from pending to files since the bugs they were
watching for seem to be fixed. Moved some other test cases from pending
to disabled because they deceptively claim to pass while investigation
reveals the ticket needs to remain open. Closes #1996, #2660.
|
|
|
|
|
| |
Disabled docgenerator test, which isn't compatible with Scaladoc 2.
|
|
|
|
|
|
| |
Moved disabled tests back into their original place. Expect 7 tests to
fail.
|
| |
|
|
|
|
|
| |
Disabling another test trying to unhang the test suite.
|
|
|
|
|
| |
Disabled an actor test which is hanging the test suite.
|
|
|
|
|
|
|
|
| |
[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.
|
|
|
|
|
|
| |
The first working scalacheck test! Now Arbitrary is working for us
instead of our nemesis Capt. Entropy.
|