Skip to content

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

Closed
odersky opened this issue Nov 8, 2015 · 9 comments
Closed

partest should implement --failed correctly #930

odersky opened this issue Nov 8, 2015 · 9 comments

Comments

@odersky
Copy link
Contributor

odersky commented Nov 8, 2015

It would be really helpful to have a mode where partest runs only failed tests.

@odersky
Copy link
Contributor Author

odersky commented Nov 19, 2015

More items on the partest wishlist:

  • Provide a log per test, instead of piping everything into one output stream
  • Honor xxx.flags files when performing junit tests
  • Have a cleaned up output like the original partest

@DarkDimius
Copy link
Contributor

Honor xxx.flags files when performing junit tests

AFAIK this is implemented. Flags are generated from junit config.
Otherwise many tests requiring -language:Scala2 would fail.

@odersky
Copy link
Contributor Author

odersky commented Nov 19, 2015

It would be good to have a test for this. I tried something with -language:Scala2 and it did not work.

@DarkDimius
Copy link
Contributor

We do have tests for this. For example compileStdLib test https://scala-ci.typesafe.com/job/dotty-master-validate-partest/708/consoleFull .
Here the excerpt from log:

/home/jenkins/workspace/dotty-master-validate-partest/tests/partest-generated/pos/compileStdLib/Signalling.scala:89: 
migration warning: Procedure syntax no longer supported; `=' should be inserted here
 def setIndexFlagIfGreater(f: Int)
 ^

This would have been an error if partest did not pass -language:Scala2

@odersky
Copy link
Contributor Author

odersky commented Nov 19, 2015

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.

@DarkDimius
Copy link
Contributor

@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.
My workflow is based around attaching debugger to junit tests.

@smarter
Copy link
Member

smarter commented Nov 19, 2015

junit also honors the flags, otherwise the same tests would fail in junit.

Are you sure? Doesn't junit work because we explicitly pass the scala2 mode flag in tests.scala:

@Test def compileStdLib = compileList("compileStdLib", stdlibFiles, "-migration" :: scala2mode)

@DarkDimius
Copy link
Contributor

@smarter partest flags are generated from ones that you explicitly pass to junit. Not the reverse.

@smarter
Copy link
Member

smarter commented Jan 10, 2018

Partest is dead, but let's open an issue for having this feature in vulpix: #3798

@smarter smarter closed this as completed Jan 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants