Build flake "PluginProblemReporter.createPluginExceptionByClass" [295943415]

Assigned

Bug

Status Update

No update yet.

Description

au...@google.com

created issue #1

Aug 14, 2023 10:14PM

Detected these failing tasks: [':docs-public:docs']
> Task :docs-public:docs
Exception in thread "main" java.lang.NullPointerException: Cannot invoke "com.intellij.diagnostic.PluginProblemReporter.createPluginExceptionByClass(String, java.lang.Throwable, java.lang.Class)" because the return value of "com.intellij.diagnostic.PluginProblemReporter.getInstance()" is null
at com.intellij.diagnostic.PluginException.createByClass(PluginException.java:83)
at com.intellij.util.IdempotenceChecker.reportFailure(IdempotenceChecker.java:90)
at com.intellij.util.IdempotenceChecker.checkEquivalence(IdempotenceChecker.java:77)
at com.intellij.psi.impl.source.resolve.ResolveCache.cache(ResolveCache.java:322)
at com.intellij.psi.impl.source.resolve.ResolveCache.resolve(ResolveCache.java:249)
at com.intellij.psi.impl.source.resolve.ResolveCache.resolveWithCaching(ResolveCache.java:184)
at com.intellij.psi.impl.PsiImplUtil.multiResolveImpl(PsiImplUtil.java:789)
at com.intellij.psi.impl.PsiImplUtil.multiResolveImpl(PsiImplUtil.java:781)
at com.intellij.psi.impl.PsiImplUtil.multiResolveImpl(PsiImplUtil.java:757)
at com.intellij.psi.impl.source.PsiJavaCodeReferenceElementImpl.multiResolve(PsiJavaCodeReferenceElementImpl.java:429)
at com.intellij.psi.impl.source.PsiJavaCodeReferenceElementImpl.advancedResolve(PsiJavaCodeReferenceElementImpl.java:423)
at com.intellij.psi.impl.source.PsiClassReferenceType.resolveGenerics(PsiClassReferenceType.java:177)
at com.intellij.psi.impl.source.PsiClassReferenceType.resolve(PsiClassReferenceType.java:121)
at org.jetbrains.dokka.base.translators.psi.DefaultPsiToDocumentableTranslator$DokkaPsiParser$parseClasslike$2$invokeSuspend$$inlined$with$lambda$2.invoke(DefaultPsiToDocumentableTranslator.kt:171)
at org.jetbrains.dokka.base.translators.psi.DefaultPsiToDocumentableTranslator$DokkaPsiParser$parseClasslike$2$invokeSuspend$$inlined$with$lambda$3.invoke(DefaultPsiToDocumentableTranslator.kt:203)
at org.jetbrains.dokka.base.translators.psi.DefaultPsiToDocumentableTranslator$DokkaPsiParser$parseClasslike$2.invokeSuspend(DefaultPsiToDocumentableTranslator.kt:222)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:749)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)

FAILURE: Build failed with an exception.

* What went wrong:

https://android-build.corp.google.com/artifact/submitted/10656591/androidx/latest/view/logs%2Fbuild_error.log

Comments

ow...@google.com <ow...@google.com> #2Aug 16, 2023 03:15PM

Assigned to bu...@google.com.

I don't think this could be a bug on our end, it would have to be upstream.
No other instances on go/ab-damage-estimator.

Bugjuggler: https://github.com/Kotlin/dokka/issues/3123

bu...@google.com <bu...@google.com> #3Aug 16, 2023 03:15PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/3123 to be closed and then unassign the bug.

bu...@google.com <bu...@google.com> #4Dec 9, 2023 10:25AM

Assigned to ow...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/3123 to be closed and then unassign the bug but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/3123": harpoon URL rejected REJECTED_FC_TIMEOUT
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/3123": harpoon URL rejected REJECTED_SCHEDULE_TIME_OVER_DEADLINE

ow...@google.com <ow...@google.com> #5Dec 26, 2023 02:22PM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/3123

bu...@google.com <bu...@google.com> #6Dec 26, 2023 02:22PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/3123 to be closed and then assign the bug to owengray@google.com.

bu...@google.com <bu...@google.com> #7May 29, 2024 01:45PM

Assigned to ow...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/3123 to be closed and then assign the bug to owengray@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/3123": harpoon URL rejected REJECTED_FC_TIMEOUT
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/3123": harpoon URL rejected REJECTED_FC_TOO_MANY_PENDING
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/3123": harpoon URL rejected REJECTED_SCHEDULE_TIME_OVER_DEADLINE

ow...@google.com <ow...@google.com> #8Jun 5, 2024 05:05PM

Reassigned to bu...@google.com.

Bugjuggler: https://github.com/Kotlin/dokka/issues/3123

bu...@google.com <bu...@google.com> #9Jun 5, 2024 05:05PM

Accepted by bu...@google.com.

Hi. I've received your bug and will wait for

https://github.com/Kotlin/dokka/issues/3123 to be closed and then assign the bug to owengray@google.com.

bu...@google.com <bu...@google.com> #10Sep 24, 2024 03:01PM

Assigned to ow...@google.com.

I've seen too many errors and am giving up, sorry.

I should wait for

https://github.com/Kotlin/dokka/issues/3123 to be closed and then assign the bug to owengray@google.com but encountered:
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/3123": harpoon URL rejected REJECTED_FC_TIMEOUT
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/3123": harpoon URL rejected REJECTED_SCHEDULE_TIME_OVER_DEADLINE
* github.Issue: Get "

https://api.github.com/repos/Kotlin/dokka/issues/3123": harpoon URL rejected REJECTED_FC_TOO_MANY_PENDING

Issue 295943415

Description

Issue summary

Comments

ow...@google.com <ow...@google.com> #2Aug 16, 2023 03:15PM

bu...@google.com <bu...@google.com> #3Aug 16, 2023 03:15PM

bu...@google.com <bu...@google.com> #4Dec 9, 2023 10:25AM

ow...@google.com <ow...@google.com> #5Dec 26, 2023 02:22PM

bu...@google.com <bu...@google.com> #6Dec 26, 2023 02:22PM

bu...@google.com <bu...@google.com> #7May 29, 2024 01:45PM

ow...@google.com <ow...@google.com> #8Jun 5, 2024 05:05PM

bu...@google.com <bu...@google.com> #9Jun 5, 2024 05:05PM

bu...@google.com <bu...@google.com> #10Sep 24, 2024 03:01PM

Add comment

Issue metadata