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

LambdaDevServicesContinuousTestingTestCase.testLambda test failure #33963

Closed
machi1990 opened this issue Jun 12, 2023 · 9 comments
Closed

LambdaDevServicesContinuousTestingTestCase.testLambda test failure #33963

machi1990 opened this issue Jun 12, 2023 · 9 comments
Labels
area/amazon-lambda area/devservices area/housekeeping Issue type for generalized tasks not related to bugs or enhancements kind/bug Something isn't working

Comments

@machi1990
Copy link
Member

Describe the bug

The test io.quarkus.amazon.lambda.deployment.testing.LambdaDevServicesContinuousTestingTestCase.testLambda fails in JDK 19 as noticed in #33958 (comment).
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
Copy link

quarkus-bot bot commented Jun 12, 2023

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

@geoand geoand added the area/housekeeping Issue type for generalized tasks not related to bugs or enhancements label Jun 12, 2023
@gsmet
Copy link
Member

gsmet commented Jun 13, 2023

@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
Copy link
Member

gsmet commented Jun 13, 2023

See #34007

@patriot1burke
Copy link
Contributor

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

@gsmet
Copy link
Member

gsmet commented Jun 13, 2023

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.

gsmet added a commit to gsmet/quarkus that referenced this issue Jun 13, 2023
@stuartwdouglas
Copy link
Member

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
Copy link
Member

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
Copy link
Member

gsmet commented Jun 16, 2023

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

sberyozkin pushed a commit to sberyozkin/quarkus that referenced this issue Jun 21, 2023
@gsmet
Copy link
Member

gsmet commented Oct 2, 2024

Going to close for no activity.

@gsmet gsmet closed this as not planned Won't fix, can't repro, duplicate, stale Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/amazon-lambda area/devservices area/housekeeping Issue type for generalized tasks not related to bugs or enhancements kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants