Skip to content

[Tests] Fix incorrect k.t.assertNotNull usages#6194

Open
Filipp Zhinkin (fzhinkin) wants to merge 1 commit into
masterfrom
fzhinkin/fix-incorrect-assertnotnull-usages
Open

[Tests] Fix incorrect k.t.assertNotNull usages#6194
Filipp Zhinkin (fzhinkin) wants to merge 1 commit into
masterfrom
fzhinkin/fix-incorrect-assertnotnull-usages

Conversation

@fzhinkin

Copy link
Copy Markdown
Contributor

kotlin.test provides assertNotNull function accepting a lambda, but this lambda is not a lazy message-supplier,
but a callback invoked when the asserted value is not null.

This change fixes call sites where the lambda was
assumed to produce an error message.

See KT-86760 for details.

kotlin.test provides assertNotNull function accepting a lambda,
but this lambda is not a lazy message-supplier,
but a callback invoked when the asserted value is not null.

This change fixes call sites where the lambda was
assumed to produce an error message.

See KT-86760 for details.
@kotlin-safemerge

Copy link
Copy Markdown

@fzhinkin

Copy link
Copy Markdown
Contributor Author

/dry-run

@KotlinBuild

Build Server (KotlinBuild) commented Jun 9, 2026

Copy link
Copy Markdown

THIS IS A DRY RUN

Quality gate is triggered at https://buildserver.labs.intellij.net/build/969712548 — use this link to get full insight.

Quality gate was triggered with the following revisions:

kotlin
Branch: refs/merge/GITHUB-6194/safe-merge
Commit: 50f2357


Quality gate failed. See https://buildserver.labs.intellij.net/build/969712548 to get full insight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants