quarkusio / quarkus

Quarkus: Supersonic Subatomic Java.
https://quarkus.io
Apache License 2.0
13.73k stars 2.67k forks source link

LambdaDevServicesContinuousTestingTestCase.testLambda test failure #33963

Closed machi1990 closed 2 weeks ago

machi1990 commented 1 year ago

Describe the bug

The test io.quarkus.amazon.lambda.deployment.testing.LambdaDevServicesContinuousTestingTestCase.testLambda fails in JDK 19 as noticed in https://github.com/quarkusio/quarkus/pull/33958#issuecomment-1586481744. The failure report is

org.opentest4j.AssertionFailedError: expected: <1> but was: <0>
    at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
    at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

Expected behavior

The test should pass consistently

Actual behavior

The test fails as can be seen in the linked PR

How to Reproduce?

No response

Output of uname -a or ver

CI

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

quarkus-bot[bot] commented 1 year ago

/cc @geoand (devservices), @matejvasek (amazon-lambda), @patriot1burke (amazon-lambda), @stuartwdouglas (devservices)

gsmet commented 1 year ago

@patriot1burke I will disable this test as it is causing a lot of CI failures and it makes it harder for us to make progress.

gsmet commented 1 year ago

See https://github.com/quarkusio/quarkus/pull/34007

patriot1burke commented 1 year ago

This stuff was committed a long time ago. Was this test always failing? If not, then, you could be masking something deeper.

gsmet commented 1 year ago

It failed a lot more often lately. I don't know if it failed before that.

It needs to be handled but for now we need CI to be more stable than it is because mainly of this failure.

stuartwdouglas commented 1 year ago

This would be why it is failing, the test is basically hanging:

2023-06-11T23:55:50.6986235Z 2023-06-11 23:55:50,686 ERROR [io.qua.test] (Test runner thread) Test LambdaHandlerET#testSimpleLambdaSuccess() failed 
2023-06-11T23:55:50.6986627Z : java.net.SocketTimeoutException: Read timed out
2023-06-11T23:55:50.6987061Z    at io.restassured.internal.RequestSpecificationImpl.post(RequestSpecificationImpl.groovy)
2023-06-11T23:55:50.6987840Z    at io.quarkus.amazon.lambda.deployment.testing.LambdaHandlerET.testSimpleLambdaSuccess(LambdaHandlerET.java:25)
stuartwdouglas commented 1 year ago

Further context (note the timestamps):

2023-06-11T23:55:20.6540806Z 2023-06-11 23:55:20,646 DEBUG [io.qua.ama.lam.run.MockEventServer] (vert.x-worker-thread-7) Starting processing 15517ecf-551c-42d4-b0fe-e4c62a12eec0, added to pending request map
2023-06-11T23:55:50.6983092Z 2023-06-11 23:55:50,679 INFO  [io.quarkus] (Test runner thread) quarkus-amazon-lambda-deployment(test application) stopped in 0.001s
gsmet commented 1 year ago

It's disabled now, it was really in our way. Please have a look ASAP so that we can enable it again.

gsmet commented 2 weeks ago

Going to close for no activity.