Skip to content

Add ID attribute to a button for starting continuous testing so that DEV UI tests select the button and start testing using DEV UI #48030

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

Conversation

michalvavrik
Copy link
Member

With #47952 starting continuous testing using the start button in the qwc-continuous-testing-menu-action.js component became less reliable (during testing where millis matter) as clicking on button as soon as the menu was rendered didn't result in starting the tests. Waiting tiny little bit helped, but I'd like to be able to refer to the Start button as suggested here #47952 (comment), which could help determine the right time when to click on the button.

This comment has been minimized.

@michalvavrik
Copy link
Member Author

Something tells me the failures are unrelated :-).

Copy link

quarkus-bot bot commented May 24, 2025

Status for workflow Quarkus CI

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

Failing Jobs

Status Name Step Failures Logs Raw logs Build scan
Native Tests - Data1 Build ⚠️ Check → Logs Raw logs 🚧
Native Tests - Data7 Build ⚠️ Check → Logs Raw logs 🚧
JVM Integration Tests - JDK 17 Build Failures Logs Raw logs 🔍
✔️ JVM Integration Tests - JDK 17 Windows Logs Raw logs 🚧
JVM Integration Tests - JDK 21 Build ⚠️ Check → Logs Raw logs 🚧

You can consult the Develocity build scans.

Failures

⚙️ JVM Integration Tests - JDK 17 #

- Failing: integration-tests/hibernate-orm-tenancy/connection-resolver integration-tests/hibernate-orm-tenancy/connection-resolver-legacy-qualifiers integration-tests/hibernate-orm-tenancy/datasource and 2 more

📦 integration-tests/hibernate-orm-tenancy/connection-resolver

Failed to execute goal io.fabric8:docker-maven-plugin:0.46.0:start (docker-start) on project quarkus-integration-test-hibernate-orm-tenancy-connection-resolver: I/O Error

📦 integration-tests/hibernate-orm-tenancy/connection-resolver-legacy-qualifiers

Failed to execute goal io.fabric8:docker-maven-plugin:0.46.0:start (docker-start) on project quarkus-integration-test-hibernate-orm-tenancy-connection-resolver-legacy-qualifiers: I/O Error

📦 integration-tests/hibernate-orm-tenancy/datasource

Failed to execute goal io.fabric8:docker-maven-plugin:0.46.0:start (docker-start) on project quarkus-integration-test-hibernate-orm-tenancy-datasource: I/O Error

📦 integration-tests/jpa-mariadb

Failed to execute goal io.fabric8:docker-maven-plugin:0.46.0:start (docker-start) on project quarkus-integration-test-jpa-mariadb: I/O Error

📦 integration-tests/reactive-mysql-client

Failed to execute goal io.fabric8:docker-maven-plugin:0.46.0:start (docker-start) on project quarkus-integration-test-reactive-mysql-client: I/O Error


Flaky tests - Develocity

⚙️ JVM Integration Tests - JDK 17

📦 integration-tests/opentelemetry

io.quarkus.it.opentelemetry.LoggingResourceTest.testException - History

  • Condition with Lambda expression in io.quarkus.it.opentelemetry.LoggingResourceTest was not fulfilled within 2 minutes. - org.awaitility.core.ConditionTimeoutException
org.awaitility.core.ConditionTimeoutException: Condition with Lambda expression in io.quarkus.it.opentelemetry.LoggingResourceTest was not fulfilled within 2 minutes.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
	at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1160)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1129)
	at io.quarkus.it.opentelemetry.LoggingResourceTest.testException(LoggingResourceTest.java:113)
	at java.base/java.lang.reflect.Method.invoke(Method.java:569)

📦 integration-tests/opentelemetry-grpc-only

io.quarkus.it.opentelemetry.grpc.HelloGrpcClientTest.testHello - History

  • java.lang.RuntimeException: Failed to start quarkus - java.lang.RuntimeException
java.lang.RuntimeException: java.lang.RuntimeException: Failed to start quarkus
	at io.quarkus.test.junit.QuarkusTestExtension.throwBootFailureException(QuarkusTestExtension.java:668)
	at io.quarkus.test.junit.QuarkusTestExtension.interceptTestClassConstructor(QuarkusTestExtension.java:763)
	at java.base/java.util.Optional.orElseGet(Optional.java:364)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1511)
Caused by: java.lang.RuntimeException: Failed to start quarkus
	at io.quarkus.runner.ApplicationImpl.doStart(Unknown Source)

@gastaldi gastaldi merged commit e58a5f3 into quarkusio:main May 24, 2025
53 of 57 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.24 - main milestone May 24, 2025
@michalvavrik michalvavrik deleted the feature/add-dev-ui-hook-for-continuous-testing branch May 24, 2025 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants