Uploaded image for project: 'Quarkus'
  1. Quarkus
  2. QUARKUS-6793

[Migration to 3.27] Random test failures during the CI

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 3.27.2.GA
    • None
    • team/eng
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ---

      Per cu.

      ~~~

      we wanted to report that since our move to the community version Quarkus 3.27.0 we are encountering random CI failures with messages like:

      • java.lang.NullPointerException: Cannot invoke "io.quarkus.arc.ArcContainer.getCurrentContextFactory()" because the return value of "io.quarkus.arc.Arc.container()" is null
      • java.lang.RuntimeException: Internal errror: shutdownContext is null. This probably happened because Quarkus failed to start properly in an earlier step, or because tests were run on a Quarkus instance that had already been shut down.
        Someone else and us have reported issues to the open source community:

      https://github.com/quarkusio/quarkus/issues/50661

       

      https://github.com/quarkusio/quarkus/issues/50740

      But we wanted you to make clearly the link between the issues and us, to highlight that a fix for those issues is essential for us to adopt Quarkus 3.27.
      Thanks and best regards, Emile.

      Describe the impact to you or the business
      Blocking the migration to Quarkus 3.27 of all internal products based on Quarkus.

      In what environment are you experiencing this behavior?

      ~~~

      Is this a known issue ? KIndly advise.

              rh-ee-hcummins Holly Cummins
              rhn-support-asaji Anu Saji
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: