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

Check for server not starting in TCK FATs #30307

Open
wants to merge 1 commit into
base: integration
Choose a base branch
from

Conversation

Azquelt
Copy link
Member

@Azquelt Azquelt commented Nov 27, 2024

We're seeing some TCK FATs fail in the certification build when they run against servers which don't have the necessary features.

Fixes #30306

We're seeing some TCK FATs fail in the certification build when they run
against servers which don't have the necessary features.
@Azquelt
Copy link
Member Author

Azquelt commented Nov 27, 2024

Run a build with all TCK FATs in full mode.

!build
!spawn.fullfat.buckets=com.ibm.ws.concurrent.mp.1.2_fat_tck,com.ibm.ws.concurrent.mp.1.3_fat_tck,com.ibm.ws.concurrent.mp_fat_tck,com.ibm.ws.microprofile.config.1.1_fat_tck,com.ibm.ws.microprofile.config.1.2_fat_tck,com.ibm.ws.microprofile.config.1.3_fat_tck,com.ibm.ws.microprofile.config.1.4_fat_tck,com.ibm.ws.microprofile.faulttolerance.1.1_fat_tck,com.ibm.ws.microprofile.faulttolerance.2.0_fat_tck,com.ibm.ws.microprofile.faulttolerance.2.1_fat_tck,com.ibm.ws.microprofile.faulttolerance_fat_tck,com.ibm.ws.microprofile.graphql_fat_tck,com.ibm.ws.microprofile.health.1.0_fat_tck,com.ibm.ws.microprofile.health.2.0_fat_tck,com.ibm.ws.microprofile.health.2.1_fat_tck,com.ibm.ws.microprofile.health.2.2_fat_tck,com.ibm.ws.microprofile.metrics.1.1_fat_tck,com.ibm.ws.microprofile.metrics.1.1.noAuth_fat_tck,com.ibm.ws.microprofile.metrics.2.0_fat_tck,com.ibm.ws.microprofile.metrics.2.2_fat_tck,com.ibm.ws.microprofile.metrics.2.3_fat_tck,com.ibm.ws.microprofile.metrics_fat_tck,com.ibm.ws.microprofile.mpjwt.1.0_fat_tck,com.ibm.ws.microprofile.mpjwt.1.1_fat_tck,com.ibm.ws.microprofile.openapi.1.1_fat_tck,com.ibm.ws.microprofile.openapi_fat_tck,com.ibm.ws.microprofile.opentracing.1.1_fat_tck,com.ibm.ws.microprofile.opentracing.1.2_fat_tck,com.ibm.ws.microprofile.opentracing.1.3_fat_tck,com.ibm.ws.microprofile.opentracing_fat_tck,com.ibm.ws.microprofile.reactive.messaging_fat_tck,com.ibm.ws.microprofile.reactive.streams.operators_fat_tck,com.ibm.ws.microprofile.rest.client11_fat_tck,com.ibm.ws.microprofile.rest.client12_fat_tck,com.ibm.ws.microprofile.rest.client13_fat_tck,com.ibm.ws.microprofile.rest.client14_fat_tck,com.ibm.ws.microprofile.rest.client_fat_tck,com.ibm.ws.security.mp.jwt_fat_tck,io.openliberty.jakarta.concurrency.3.0_fat_tck,io.openliberty.jakarta.concurrency.3.1_fat_tck,io.openliberty.jakarta.data.1.0_fat_tck,io.openliberty.jakarta.jsonb.3.0_fat_tck,io.openliberty.jakarta.jsonp.2.1_fat_tck,io.openliberty.jakarta.rest.3.1.internal_fat_tck,io.openliberty.jakarta.rest.4.0.internal_fat_tck,io.openliberty.jakarta.validation.3.1_fat_tck,io.openliberty.microprofile.config.2.0.internal_fat_tck,io.openliberty.microprofile.config.3.0.internal_fat_tck,io.openliberty.microprofile.config.3.1.internal_fat_tck,io.openliberty.microprofile.faulttolerance.3.0.internal_fat_tck,io.openliberty.microprofile.faulttolerance.4.0.internal_fat_tck,io.openliberty.microprofile.faulttolerance.4.1.internal_fat_tck,io.openliberty.microprofile.graphql.2.0.internal_fat_tck,io.openliberty.microprofile.health.3.0.internal_fat_tck,io.openliberty.microprofile.health.3.1.internal_fat_tck,io.openliberty.microprofile.health.4.0.internal_fat_tck,io.openliberty.microprofile.jwt.1.2.internal_fat_tck,io.openliberty.microprofile.jwt.2.0.internal_fat_tck,io.openliberty.microprofile.jwt.2.1.internal_fat_tck,io.openliberty.microprofile.lra.1.0.internal_fat_tck,io.openliberty.microprofile.metrics.internal.3.0_fat_tck,io.openliberty.microprofile.metrics.internal.4.0_fat_tck,io.openliberty.microprofile.metrics.internal.5.0_fat_tck,io.openliberty.microprofile.metrics.internal.5.1_fat_tck,io.openliberty.microprofile.openapi.2.0.internal_fat_tck,io.openliberty.microprofile.openapi.3.0.internal_fat_tck,io.openliberty.microprofile.openapi.3.1.internal_fat_tck,io.openliberty.microprofile.openapi.4.0.internal_fat_tck,io.openliberty.microprofile.opentracing.2.0.internal_fat_tck,io.openliberty.microprofile.opentracing.3.0.internal_fat_tck,io.openliberty.microprofile.reactive.messaging30.internal_fat_tck,io.openliberty.microprofile.reactive.streams.operators30.internal_fat_tck,io.openliberty.microprofile.rest.client.2.0.internal_fat_tck,io.openliberty.microprofile.rest.client.3.0.internal_fat_tck,io.openliberty.microprofile.rest.client.4.0.internal_fat_tck,io.openliberty.microprofile.telemetry.1.0.internal_fat_tck,io.openliberty.microprofile.telemetry.1.1.internal_fat_tck,io.openliberty.microprofile.telemetry.2.0.internal_fat_tck

@LibbyBot
Copy link

Your personal pipeline request is at https://libh-proxy1.fyre.ibm.com/cognitive/pipelineAnalysis.html?uuid=3d423d96-d7f0-42a0-8e8b-33441cf01f64

Target locations of links might be accessible only to IBM employees.

@LibbyBot
Copy link

Code analysis and actions

DO NOT DELETE THIS COMMENT.
  • Please describe in a separate comment how you tested your changes.

  • 2 test infrastructure code files were changed.

  • Test failures/errors in the build could be due to these changes.

@LibbyBot
Copy link

@Azquelt
Copy link
Member Author

Azquelt commented Nov 28, 2024

!build
(view Open Liberty Personal Build - ❌ completed with errors/failures.)
spawn.fullfat.buckets=com.ibm.ws.concurrent.mp.1.2_fat_tck,com.ibm.ws.concurrent.mp.1.3_fat_tck,com.ibm.ws.concurrent.mp_fat_tck,com.ibm.ws.microprofile.config.1.1_fat_tck,com.ibm.ws.microprofile.config.1.2_fat_tck,com.ibm.ws.microprofile.config.1.3_fat_tck,com.ibm.ws.microprofile.config.1.4_fat_tck,com.ibm.ws.microprofile.faulttolerance.1.1_fat_tck,com.ibm.ws.microprofile.faulttolerance.2.0_fat_tck,com.ibm.ws.microprofile.faulttolerance.2.1_fat_tck,com.ibm.ws.microprofile.faulttolerance_fat_tck,com.ibm.ws.microprofile.graphql_fat_tck,com.ibm.ws.microprofile.health.1.0_fat_tck,com.ibm.ws.microprofile.health.2.0_fat_tck,com.ibm.ws.microprofile.health.2.1_fat_tck,com.ibm.ws.microprofile.health.2.2_fat_tck,com.ibm.ws.microprofile.metrics.1.1_fat_tck,com.ibm.ws.microprofile.metrics.1.1.noAuth_fat_tck,com.ibm.ws.microprofile.metrics.2.0_fat_tck,com.ibm.ws.microprofile.metrics.2.2_fat_tck,com.ibm.ws.microprofile.metrics.2.3_fat_tck,com.ibm.ws.microprofile.metrics_fat_tck,com.ibm.ws.microprofile.mpjwt.1.0_fat_tck,com.ibm.ws.microprofile.mpjwt.1.1_fat_tck,com.ibm.ws.microprofile.openapi.1.1_fat_tck,com.ibm.ws.microprofile.openapi_fat_tck,com.ibm.ws.microprofile.opentracing.1.1_fat_tck,com.ibm.ws.microprofile.opentracing.1.2_fat_tck,com.ibm.ws.microprofile.opentracing.1.3_fat_tck,com.ibm.ws.microprofile.opentracing_fat_tck,com.ibm.ws.microprofile.reactive.messaging_fat_tck,com.ibm.ws.microprofile.reactive.streams.operators_fat_tck,com.ibm.ws.microprofile.rest.client11_fat_tck,com.ibm.ws.microprofile.rest.client12_fat_tck,com.ibm.ws.microprofile.rest.client13_fat_tck,com.ibm.ws.microprofile.rest.client14_fat_tck,com.ibm.ws.microprofile.rest.client_fat_tck,com.ibm.ws.security.mp.jwt_fat_tck,io.openliberty.jakarta.concurrency.3.0_fat_tck,io.openliberty.jakarta.concurrency.3.1_fat_tck,io.openliberty.jakarta.data.1.0_fat_tck,io.openliberty.jakarta.jsonb.3.0_fat_tck,io.openliberty.jakarta.jsonp.2.1_fat_tck,io.openliberty.jakarta.rest.3.1.internal_fat_tck,io.openliberty.jakarta.rest.4.0.internal_fat_tck,io.openliberty.jakarta.validation.3.1_fat_tck,io.openliberty.microprofile.config.2.0.internal_fat_tck,io.openliberty.microprofile.config.3.0.internal_fat_tck,io.openliberty.microprofile.config.3.1.internal_fat_tck,io.openliberty.microprofile.faulttolerance.3.0.internal_fat_tck,io.openliberty.microprofile.faulttolerance.4.0.internal_fat_tck,io.openliberty.microprofile.faulttolerance.4.1.internal_fat_tck,io.openliberty.microprofile.graphql.2.0.internal_fat_tck,io.openliberty.microprofile.health.3.0.internal_fat_tck,io.openliberty.microprofile.health.3.1.internal_fat_tck,io.openliberty.microprofile.health.4.0.internal_fat_tck,io.openliberty.microprofile.jwt.1.2.internal_fat_tck,io.openliberty.microprofile.jwt.2.0.internal_fat_tck,io.openliberty.microprofile.jwt.2.1.internal_fat_tck,io.openliberty.microprofile.lra.1.0.internal_fat_tck,io.openliberty.microprofile.metrics.internal.3.0_fat_tck,io.openliberty.microprofile.metrics.internal.4.0_fat_tck,io.openliberty.microprofile.metrics.internal.5.0_fat_tck,io.openliberty.microprofile.metrics.internal.5.1_fat_tck,io.openliberty.microprofile.openapi.2.0.internal_fat_tck,io.openliberty.microprofile.openapi.3.0.internal_fat_tck,io.openliberty.microprofile.openapi.3.1.internal_fat_tck,io.openliberty.microprofile.openapi.4.0.internal_fat_tck,io.openliberty.microprofile.opentracing.2.0.internal_fat_tck,io.openliberty.microprofile.opentracing.3.0.internal_fat_tck,io.openliberty.microprofile.reactive.messaging30.internal_fat_tck,io.openliberty.microprofile.reactive.streams.operators30.internal_fat_tck,io.openliberty.microprofile.rest.client.2.0.internal_fat_tck,io.openliberty.microprofile.rest.client.3.0.internal_fat_tck,io.openliberty.microprofile.rest.client.4.0.internal_fat_tck,io.openliberty.microprofile.telemetry.1.0.internal_fat_tck,io.openliberty.microprofile.telemetry.1.1.internal_fat_tck,io.openliberty.microprofile.telemetry.2.0.internal_fat_tck

@LibbyBot
Copy link

Code analysis and actions

DO NOT DELETE THIS COMMENT.
  • 2 test infrastructure code files were changed.

  • Test failures/errors in the build could be due to these changes.

  • Please describe in a separate comment how you tested your changes.

@Azquelt
Copy link
Member Author

Azquelt commented Nov 28, 2024

@Azquelt
Copy link
Member Author

Azquelt commented Nov 29, 2024

MP Compliance pipeline looks good. We now get a more useful error when the server fails to start properly.

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.

Detect if server fails to start properly in TCK FATs
2 participants