-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Update reference, MiMa previous version and sync TASTy version #22187
Update reference, MiMa previous version and sync TASTy version #22187
Conversation
|
||
// Tested only in nightly / release builds | ||
// Protects from publishing artifacts with incorrect TASTY version | ||
@Test def testReleasedTastyVersion(): Unit = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test actually would be never executed - RELEASEBUILD and NIGHTLYBUILD are set only for the release but not in tests executed as a requirement to start releasing job
…d before releasing artifacts
glad there's finally a real test :) |
@Test def testBuildTastyVersion(): Unit = { | ||
val expectedVersion = sys.env.get(ExpectedTastyVersionEnvVar) | ||
.getOrElse(fail(s"Env variable $ExpectedTastyVersionEnvVar not defined")) | ||
.match { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this test even run? This is not valid syntax...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
foo.match {...}
is a valid alternative syntax for foo match {...}
in scala 3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
28.7-experimental-1
- it should have been set when branching of 3.6.3.Reference version and TASTy version bump needs to be performed at the same time (otherwise usage of compiler with stable TASTY would lead to failure in from-tasty non-bootstrapped tests)
[test_non_bootstrapped]