-
Notifications
You must be signed in to change notification settings - Fork 1.1k
partest should implement --failed correctly #930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
More items on the partest wishlist:
|
AFAIK this is implemented. Flags are generated from junit config. |
It would be good to have a test for this. I tried something with -language:Scala2 and it did not work. |
We do have tests for this. For example compileStdLib test https://scala-ci.typesafe.com/job/dotty-master-validate-partest/708/consoleFull .
This would have been an error if partest did not pass |
Ah, then it was probably the junit test that failed. But given that junit cannot honor the flags, maybe we should stop using it? I would switch tomorrow if partest's test output was acceptably nice. |
@odersky junit also honors the flags, otherwise the same tests would fail in junit. I'd like to continue with being able to choose to run tests either in partest or junit. |
Are you sure? Doesn't junit work because we explicitly pass the scala2 mode flag in @Test def compileStdLib = compileList("compileStdLib", stdlibFiles, "-migration" :: scala2mode) |
@smarter partest flags are generated from ones that you explicitly pass to junit. Not the reverse. |
Partest is dead, but let's open an issue for having this feature in vulpix: #3798 |
It would be really helpful to have a mode where partest runs only failed tests.
The text was updated successfully, but these errors were encountered: