Skip to content
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

Make sure generated quarkus-artifact.properties is stable #41587

Merged
merged 1 commit into from
Jul 1, 2024

Conversation

gsmet
Copy link
Member

@gsmet gsmet commented Jul 1, 2024

At the moment, it contains a timestamp, which is going to be in the way of the cache.
Also make sure the properties are sorted.

/cc @jprinet

At the moment, it contains a timestamp, which is going to be in the way
of the cache.
Also make sure the properties are sorted.
@gsmet gsmet requested a review from aloubyansky July 1, 2024 14:33
@quarkus-bot quarkus-bot bot added area/core area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins labels Jul 1, 2024
gsmet added a commit to gsmet/develocity-build-config-samples that referenced this pull request Jul 1, 2024
When running ITs for native, we need quarkus-artifact.properties to be
around so it needs to be part of the cache.

Also make it an input of Failsafe.
This file contains a relative path to the binary to run and a few
additional metadata such as the full GraalVM version.
Whenever this version has changed, we need to run the tests again so it
makes sense to make it an input.

Note that we will need quarkusio/quarkus#41587
to be in so that quarkus-artifact.properties doesn't contain a
timestamp.
gsmet added a commit to gsmet/develocity-build-config-samples that referenced this pull request Jul 1, 2024
When running ITs for native, we need quarkus-artifact.properties to be
around so it needs to be part of the cache.

Also make it an input of Failsafe.
This file contains a relative path to the binary to run and a few
additional metadata such as the full GraalVM version.
Whenever this version has changed, we need to run the tests again so it
makes sense to make it an input.

Note that we will need quarkusio/quarkus#41587
to be in so that quarkus-artifact.properties doesn't contain a
timestamp.

Signed-off-by: Guillaume Smet <guillaume.smet@gmail.com>
@jprinet
Copy link
Contributor

jprinet commented Jul 1, 2024

The timestamp is actually not a problem as the file is not a direct input, its entries are parsed and used to create a list of inputs

The sorting is important though as the order matters on compile classpath normalization.
More details available here

@gsmet
Copy link
Member Author

gsmet commented Jul 1, 2024

@jprinet I actually made it an input of the Failsafe goal in gradle/develocity-build-config-samples#1280. But I can drop it from the extension PR if you think it's better not to have it as an input.

That being said, even if we don't make it an input, I would prefer this PR to go in.

jprinet pushed a commit to gradle/develocity-build-config-samples that referenced this pull request Jul 1, 2024
* Add quarkus-artifact.properties as an output of quarkus:build

When running ITs for native, we need quarkus-artifact.properties to be
around so it needs to be part of the cache.

Also make it an input of Failsafe.
This file contains a relative path to the binary to run and a few
additional metadata such as the full GraalVM version.
Whenever this version has changed, we need to run the tests again so it
makes sense to make it an input.

Note that we will need quarkusio/quarkus#41587
to be in so that quarkus-artifact.properties doesn't contain a
timestamp.

Signed-off-by: Guillaume Smet <guillaume.smet@gmail.com>

* Do not register quarkus-artifact.properties as input of Failsafe

Signed-off-by: Guillaume Smet <guillaume.smet@gmail.com>

---------

Signed-off-by: Guillaume Smet <guillaume.smet@gmail.com>
@gsmet gsmet merged commit c54bc15 into quarkusio:main Jul 1, 2024
52 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.13 - main milestone Jul 1, 2024
Copy link

quarkus-bot bot commented Jul 1, 2024

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 6981dab.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.


Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 extensions/smallrye-reactive-messaging-kafka/deployment

io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase.sseStream - History

  • Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase Expecting size of: [] to be greater than or equal to 2 but was 0 within 10 seconds. - org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: 
Assertion condition defined as a Lambda expression in io.quarkus.smallrye.reactivemessaging.kafka.deployment.dev.KafkaDevServicesDevModeTestCase 
Expecting size of:
  []
to be greater than or equal to 2 but was 0 within 10 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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core area/devtools Issues/PR related to maven, gradle, platform and cli tooling/plugins triage/flaky-test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants