Skip to content

Idempotency tests should use forked JVMs #7094

Open
@smarter

Description

@smarter

Currently, https://github.com/lampepfl/dotty/blob/master/compiler/test/dotty/tools/dotc/IdempotencyTests.scala calls compileFilesInDir and compieList which will run Dotty in the current JVM, but some instabilities may only become apparent when the same code is compiled using different JVMs (in paticular because it means that all objects will get different identityHashCode, which will lead to sets being ordered and traversed in different orders, etc). So to make the idempotency tests more robust they should start a new java process each time they want to compile the same code again (different pieces of code can still be compiled with the same JVM to keep the tests fast).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions