Anyone know why classic frontend diagnostics tests are no longer working in 2.0.0-Beta1? Some kind of new config that I am missing?

What do you mean by "no longer working"?

All tests are failing in 2.0.0-Beta1. None of the diagnostics are present in the output.

We still use them in master, so nothing wasn't broken intentionally Some stack trace maybe helpful

Yeah I noticed similar tests in master (that haven’t changed much since I based my tests on them). A stack trace in case it points to any obvious issues:

@dmitriy.dolovov Could you help with it?

Found another change related to DiagnosticsNativeTests and stdlib. Not sure why it’s needed/what it’s supposed to do, but adding that

LibraryProvider

and the

WITH_STDLIB

directive solved it.

Yeah, native is much more internal than other internals

@Rick Clephas Hi, yes, you found a recent fix of ClassicFrontendFacade to use native stdlib instead of common stdlib. Without fix, native diagnostic test without

// WITH_STDLIB

used common stdlib and did not see

public final /*synthesized*/ val entries: kotlin.enums.EnumEntries<T>

in enums, which are unique to native stdlib. It can be seen in lines like https://github.com/JetBrains/kotlin/commit/8f03eb931467f375d1428c5b73196bf015892f54#diff-754bc0f20ca136f2868b92a96101339637ad779f805581b49edc88f8a9461468R53 So,

WITH_STDLIB

directive was permanently set, and native stdlib proper lookup now is needed for all native tests Before fix, common stdlib was used, which did not have

enumEntries

property (I guess this https://github.com/JetBrains/kotlin/blob/1564f2c549bbdff361c02f71aa128e06274336ce/core/builtins/native/kotlin/Enum.kt#L13) and now native stdlib is used, which has the property https://github.com/JetBrains/kotlin/blob/64fd4ac510f56f1d5480a1631849c1852a689d5a/kotlin-native/runtime/src/main/kotlin/kotlin/Enum.kt#L44