Skip to content

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 28, 2025

Bumps com.gradle:common-custom-user-data-maven-extension from 2.0.3 to 2.0.4.

Release notes

Sourced from com.gradle:common-custom-user-data-maven-extension's releases.

2.0.4

  • [FIX] Add GitHub run number as custom value to precisely identify GitHub Action run
Commits
  • 0abc83d [maven-release-plugin] prepare release v2.0.4
  • 538db59 Update changes.md with latest fix
  • 1831207 Merge pull request #307 from jthurne/versatility/jthurne/add-github-run-number
  • ae32aac Only add a custom value
  • 3f5284d Add a custom value for GITHUB_RUN_NUMBER
  • 1a9def1 Merge pull request #302 from gradle/dependabot/github_actions/actions/downloa...
  • e72490b Merge pull request #304 from gradle/dependabot/maven/org.apache.maven.plugins...
  • fc3b442 Merge pull request #305 from gradle/dependabot/github_actions/actions/setup-j...
  • a276e94 Bump actions/setup-java from 4 to 5
  • 8e3cb6b Bump org.apache.maven.plugins:maven-javadoc-plugin from 3.11.2 to 3.11.3
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [com.gradle:common-custom-user-data-maven-extension](https://github.com/gradle/common-custom-user-data-maven-extension) from 2.0.3 to 2.0.4.
- [Release notes](https://github.com/gradle/common-custom-user-data-maven-extension/releases)
- [Commits](gradle/common-custom-user-data-maven-extension@v2.0.3...v2.0.4)

---
updated-dependencies:
- dependency-name: com.gradle:common-custom-user-data-maven-extension
  dependency-version: 2.0.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the area/dependencies Pull requests that update a dependency file label Aug 28, 2025
Copy link

quarkus-bot bot commented Aug 29, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 2f337ad.

Failing Jobs

Status Name Step Failures Logs Raw logs Build scan
JVM Tests - JDK 17 Build Failures Logs Raw logs 🚧
✔️ JVM Tests - JDK 21 Logs Raw logs 🚧

Full information is available in the Build summary check run.
You can consult the Develocity build scans.

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: extensions/opentelemetry/deployment 
! Skipped: devtools/bom-descriptor-json extensions/liquibase/liquibase-mongodb/deployment extensions/micrometer-opentelemetry/deployment and 11 more

📦 extensions/opentelemetry/deployment

io.quarkus.opentelemetry.deployment.metrics.JvmMetricsTest. - History - More details - Source on GitHub

java.lang.RuntimeException: 
io.quarkus.builder.BuildException: Build failure: Build failed due to errors
	[error]: Build step io.quarkus.arc.deployment.ArcProcessor#validate threw an exception: java.lang.NullPointerException: Cannot invoke "io.quarkus.arc.processor.InjectionPointInfo.isProgrammaticLookup()" because "injectionPoint" is null
	at io.quarkus.arc.processor.UnusedBeans.findRemovableBeans(UnusedBeans.java:44)
	at io.quarkus.arc.processor.BeanDeployment.removeUnusedBeans(BeanDeployment.java:499)
	at io.quarkus.arc.processor.BeanDeployment.removeUnusedComponents(BeanDeployment.java:408)
	at io.quarkus.arc.processor.BeanDeployment.init(BeanDeployment.java:355)
	at io.quarkus.arc.processor.BeanProcessor.initialize(BeanProcessor.java:178)

Flaky tests - Develocity

⚙️ JVM Tests - JDK 17

📦 extensions/opentelemetry/deployment

io.quarkus.opentelemetry.deployment.logs.OtelLoggingTest.testException - History

  • Expected log to have severity <ERROR> but was <INFO> - org.opentest4j.AssertionFailedError
org.opentest4j.AssertionFailedError: Expected log to have severity <ERROR> but was <INFO>
	at io.quarkus.opentelemetry.deployment.logs.OtelLoggingTest.testException(OtelLoggingTest.java:162)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)
	at io.quarkus.test.QuarkusUnitTest.runExtensionMethod(QuarkusUnitTest.java:534)
	at io.quarkus.test.QuarkusUnitTest.interceptTestMethod(QuarkusUnitTest.java:448)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)

⚙️ JVM Tests - JDK 21

📦 extensions/smallrye-reactive-messaging/deployment

io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector - History

  • Expecting actual: ["-4","-5","-6","-7","-8","-9","-10","-11"] to start with: ["-3", "-4", "-5", "-6"] - java.lang.AssertionError
java.lang.AssertionError: 

Expecting actual:
  ["-4","-5","-6","-7","-8","-9","-10","-11"]
to start with:
  ["-3", "-4", "-5", "-6"]

	at io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector(ConnectorChangeTest.java:36)
  • Expecting actual: ["-4","-5","-6","-7","-8","-9","-10","-11"] to start with: ["-3", "-4", "-5", "-6"] - java.lang.AssertionError
java.lang.AssertionError: 

Expecting actual:
  ["-4","-5","-6","-7","-8","-9","-10","-11"]
to start with:
  ["-3", "-4", "-5", "-6"]

	at io.quarkus.smallrye.reactivemessaging.hotreload.ConnectorChangeTest.testUpdatingConnector(ConnectorChangeTest.java:36)

⚙️ JVM Tests - JDK 17 Windows

📦 extensions/opentelemetry/deployment

io.quarkus.opentelemetry.deployment.instrumentation.GraphQLOpenTelemetryTest.singleResultQueryTraceTest - History

  • Assertion condition defined as a Lambda expression in io.quarkus.opentelemetry.deployment.common.exporter.TestSpanExporter Spans: [] ==> expected: <3> but was: <0> within 5 seconds. - org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in io.quarkus.opentelemetry.deployment.common.exporter.TestSpanExporter Spans: [] ==> expected: <3> but was: <0> within 5 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
	at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
	at io.quarkus.opentelemetry.deployment.common.exporter.TestSpanExporter.assertSpanCount(TestSpanExporter.java:66)
	at io.quarkus.opentelemetry.deployment.common.exporter.TestSpanExporter_ClientProxy.assertSpanCount(Unknown Source)

📦 independent-projects/resteasy-reactive/server/vertx

org.jboss.resteasy.reactive.server.vertx.test.sse.SseServerTestCase.shouldCallOnCloseOnServer - History

  • 1 expectation failed. Response body doesn't match expectation. Expected: "true" Actual: false - java.lang.AssertionError
java.lang.AssertionError: 
1 expectation failed.
Response body doesn't match expectation.
Expected: "true"
  Actual: false

	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)

@gsmet
Copy link
Member

gsmet commented Aug 29, 2025

@manovotn we have a new java.lang.NullPointerException: Cannot invoke "io.quarkus.arc.processor.InjectionPointInfo.isProgrammaticLookup()" because "injectionPoint" is null error if the context you added can help?

Copy link
Contributor Author

dependabot bot commented on behalf of github Aug 29, 2025

Superseded by #49796.

@dependabot dependabot bot closed this Aug 29, 2025
@dependabot dependabot bot deleted the dependabot/maven/main/com.gradle-common-custom-user-data-maven-extension-2.0.4 branch August 29, 2025 21:33
@quarkus-bot quarkus-bot bot added the triage/invalid This doesn't seem right label Aug 29, 2025
@manovotn
Copy link
Contributor

manovotn commented Sep 1, 2025

@manovotn we have a new java.lang.NullPointerException: Cannot invoke "io.quarkus.arc.processor.InjectionPointInfo.isProgrammaticLookup()" because "injectionPoint" is null error if the context you added can help?

Sorry, this slipped my attention by the end of last week.
I don't remember adding any context to be fair; I however do recall looking into it and coming back completely empty handed :-/

FYI @mkouba @Ladicek^^
I know at least one of you already looked into this as well.

@mkouba
Copy link
Contributor

mkouba commented Sep 2, 2025

@manovotn we have a new java.lang.NullPointerException: Cannot invoke "io.quarkus.arc.processor.InjectionPointInfo.isProgrammaticLookup()" because "injectionPoint" is null error if the context you added can help?

Sorry, this slipped my attention by the end of last week. I don't remember adding any context to be fair; I however do recall looking into it and coming back completely empty handed :-/

FYI @mkouba @Ladicek^^ I know at least one of you already looked into this as well.

I don't remember either but I did a quick search and did not find a place where a null injection point could be added.

Is it an intermittent failure, or?

@manovotn
Copy link
Contributor

manovotn commented Sep 2, 2025

@manovotn we have a new java.lang.NullPointerException: Cannot invoke "io.quarkus.arc.processor.InjectionPointInfo.isProgrammaticLookup()" because "injectionPoint" is null error if the context you added can help?

Sorry, this slipped my attention by the end of last week. I don't remember adding any context to be fair; I however do recall looking into it and coming back completely empty handed :-/
FYI @mkouba @Ladicek^^ I know at least one of you already looked into this as well.

I don't remember either but I did a quick search and did not find a place where a null injection point could be added.

Is it an intermittent failure, or?

Yeah, every now and again this error pops up - and of course only in CI.
As far as I recall, we started paying more attention to it as part of #48331 where this null check was added.

@mkouba
Copy link
Contributor

mkouba commented Sep 2, 2025

As far as I recall, we started paying more attention to it as part of #48331 where this null check was added.

If this check is in place I don't see a way how a null injection point could be added 🤔.

@manovotn
Copy link
Contributor

manovotn commented Sep 2, 2025

As far as I recall, we started paying more attention to it as part of #48331 where this null check was added.

If this check is in place I don't see a way how a null injection point could be added 🤔.

Yea, same here.
Yet somehow, it still occurs...

By the way, there is some more info on this in #48836 as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dependencies Pull requests that update a dependency file area/gradle Gradle area/maven triage/flaky-test triage/invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants