[ZEPPELIN-6238] Prevent infinite loop in NotebookRestApiTest due to interpreter startup failure

[gurioh]

What is this PR for?

The testRunNoteNonBlocking integration test in NotebookRestApiTest can enter an infinite loop when the Python interpreter fails to start. This happens because the interpreter cannot find the python executable, resulting in an IOException: error=2, No such file or directory.

The test uses httpPost with blocking=true, followed by p1.waitUntilFinished() to wait for the paragraph to complete. When the interpreter fails to start, the paragraph's status remains in a READY state instead of transitioning to ERROR. This causes waitUntilFinished() to wait indefinitely, as isTerminated() never returns true.

The fix is to modify the test logic to immediately check the paragraph's status after p1.waitUntilFinished(). By moving the assertEquals(Job.Status.FINISHED, p1.getStatus()) assertion to immediately after the wait call, the test will fail instantly if the paragraph's status is not FINISHED (e.g., ERROR). This prevents the test from proceeding to p2.waitUntilFinished() and avoids the infinite loop.

What type of PR is it?

Bug Fix

Todos

What is the Jira issue?

*[ZEPPELIN-6238]

How should this be tested?

• Strongly recommended: add automated unit tests for any new or changed behavior
• Outline any manual steps to test the PR here.

Screenshots (if appropriate)

Questions:

• Does the license files need to update? N
• Is there breaking changes for older versions? N
• Does this needs documentation? N

[ParkGyeongTae]

Hello, thank you for your contribution!
Could you update the PR title to:
[ZEPPELIN-6238] Prevent infinite loop in NotebookRestApiTest due to interpreter startup failure
instead of the current one, Prevent infinite loop in NotebookRestApiTest due to interpreter startup failure?

[gurioh]

I’ve updated it.
Thank you for the review.

[Reamer]

The test is being tested by CI. I don't see any problems in the current master version.

[ParkGyeongTae]

I think this addition is useful, but I couldn’t reproduce the issue on my local machine. I’m using a MacBook Pro M4. Could you share what environment you were running when you saw this problem?