[TASK][EASY] Fix flaky test SessionsResourceSuite

[yaooqinn]

Code of Conduct

• I agree to follow this project's Code of Conduct

Search before creating

• I have searched in the task list and found no similar tasks.

Mentor

• I have sufficient knowledge and experience of this task, and I volunteer to be the mentor of this task to guide contributors to complete the task.

Skill requirements

• scala

Background and Goals

SessionsResourceSuite:
- open/close and count session *** FAILED ***
  1 equaled 1, but 0 did not equal 1 (SessionsResourceSuite.scala:65)
- getSessionList *** FAILED ***
  List(Map("duration" -> 0, "sessionType" -> "INTERACTIVE", "identifier" -> "96ca05ee-ecb1-49cd-a2e4-66cbf49ed343", "createTime" -> 1698822938391, "ipAddr" -> "127.0.0.1", "exception" -> "", "kyuubiInstance" -> "localhost:35415", "idleTime" -> 78, "engineId" -> "", "conf" -> Map("kyuubi.session.real.user" -> "anonymous", "testConfig" -> "testValue", "kyuubi.client.ipAddress" -> "127.0.0.1", "kyuubi.session.connection.url" -> "localhost:35415", "kyuubi.server.ipAddress" -> "localhost"), "user" -> "anonymous")) was not empty (SessionsResourceSuite.scala:104)

Implementation steps

fix these tests above that occasionally fail in CI

Additional context

No response

[davidyuan1223]

do you have this ci's complete log or url? i look the test code no problem, i need more info about the failed log

[yaooqinn]

Hi @davidyuan1223, my bad. I just remembered that I need to attach the link to the failed tests. I will update this ticket the next time I see the errors.

[yaooqinn]

https://github.com/apache/kyuubi/actions/runs/6781271541/job/18431279275?pr=5639

FYI, @davidyuan1223

[davidyuan1223]

https://github.com/apache/kyuubi/actions/runs/6781271541/job/18431279275?pr=5639

FYI, @davidyuan1223

get, you can assigned me, i will try to fix this

[yaooqinn]

Thank you @davidyuan1223

[davidyuan1223]

find root case, actually the open session is always wrong, because we use thread, so if the test case execute quickly, the thread will not execute the error location the test case finished, but because the github ci maybe execute slowly, so we can get the failed.I need more time to find the error root cause, you can add Thread.sleepe(10000) like this picture,you will get the same error

[yaooqinn]

It seems we can skip asserting activeCount

[davidyuan1223]

It seems we can skip asserting activeCount

not find the root cause and fix?

[yaooqinn]

The open session step generates a background task, if you slept for a while, it made sure that the task was submitted.

Then it's not necessary for such an unpredictable assertion.

Or we can wrap it with eventually(timeout) {}