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

Add some hint to inspect the log-level when test-launch failed #33067

Merged
merged 1 commit into from
Jun 21, 2023

Conversation

snazy
Copy link
Contributor

@snazy snazy commented May 2, 2023

Setting the log-level of a Quarkus app to WARN to even less verbose can break the detection of a successfully started application. This change just adds a note to inspect those settings to the error message(s).

@snazy
Copy link
Contributor Author

snazy commented May 2, 2023

LauncherUtil checks for both "Listening on ..." and "Quarkus ... started in ...", but those are logged at INFO. If the log level(s) are configured to WARN or higher, those messages won't be logged - even possible that the log file won't be created at all (if nothing's logged).

Doubt it's possible to have a check for this when running a test, because these settings can be "buried" in any config file in any dependency.

@quarkus-bot

This comment has been minimized.

@snazy snazy force-pushed the launcher-log-level-info branch from 58ccd2c to 6fc1f3b Compare May 3, 2023 12:30
@quarkus-bot

This comment has been minimized.

@snazy snazy force-pushed the launcher-log-level-info branch from 6fc1f3b to 8518576 Compare May 4, 2023 15:03
@quarkus-bot

This comment has been minimized.

@snazy snazy force-pushed the launcher-log-level-info branch from 8518576 to 1f93051 Compare May 12, 2023 13:00
@quarkus-bot

This comment has been minimized.

Setting the log-level of a Quarkus app to WARN to even less verbose can
break the detection of a successfully started application. This change
just adds a note to inspect those settings to the error message(s).
@gsmet gsmet force-pushed the launcher-log-level-info branch from 1f93051 to 80f6ef5 Compare June 20, 2023 17:05
Copy link
Member

@gsmet gsmet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, I rebased to get a fresh CI run.

@gsmet gsmet added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Jun 20, 2023
@quarkus-bot
Copy link

quarkus-bot bot commented Jun 21, 2023

Failing Jobs - Building 80f6ef5

Status Name Step Failures Logs Raw logs
✔️ Devtools Tests - JDK 11
Devtools Tests - JDK 11 Windows Build ⚠️ Check → Logs Raw logs
✔️ Devtools Tests - JDK 17
✔️ Maven Tests - JDK 11
Maven Tests - JDK 11 Windows Build ⚠️ Check → Logs Raw logs
Native Tests - Windows - RESTEasy Jackson Setup GraalVM ⚠️ Check → Logs Raw logs

@gsmet gsmet merged commit f57c166 into quarkusio:main Jun 21, 2023
@quarkus-bot quarkus-bot bot removed the triage/waiting-for-ci Ready to merge when CI successfully finishes label Jun 21, 2023
@quarkus-bot quarkus-bot bot added this to the 3.2 - main milestone Jun 21, 2023
@snazy snazy deleted the launcher-log-level-info branch June 21, 2023 09:06
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.

2 participants