[BEAM-12419] Deadline should be reset for each gRPC call.

[kw2542]

getState() in waitForTerminalState() is invoked multiple times and deadline should be reset each time since it is an absolute number.

Please add a meaningful description for your change here

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

ValidatesRunner compliance status (on master branch)

Lang	ULR	Dataflow	Flink	Samza	Spark	Twister2
Go	---			---		---
Java
Python	---			---		---
XLang				---		---

Examples testing status on various runners

Lang	ULR	Dataflow	Flink	Samza	Spark	Twister2
Go	---	---	---	---	---	---	---
Java	---		---	---	---	---	---
Python	---	---	---	---	---	---	---
XLang	---	---	---	---	---	---	---

Post-Commit SDK/Transform Integration Tests Status (on master branch)

Go	Java	Python

Pre-Commit Tests Status (on master branch)

---	Java	Python	Go	Website	Whitespace	Typescript
Non-portable
Portable	---			---	---	---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

[kw2542]

@apilloud Can you help take a look ?

[apilloud]

Run Java Spark PortableValidatesRunner Batch

[apilloud]

Run XVR_Spark PostCommit

[apilloud]

Run XVR_Spark3 PostCommit

[apilloud]

LGTM assuming the tests I ran pass. This will need to be cherrypicked into the 2.31.0 release branch.

[kw2542]

Run Java Spark PortableValidatesRunner Batch

I did notice that Spark PVR Streaming tests have been broken into two tests in #14483 but not for Batch tests, are we going to apply the same improvement for batch mode tests ?

[apilloud]

I'm not sure. That is probably a question for @ibzib

[ibzib]

LGTM, thanks for fixing this.

I did notice that Spark PVR Streaming tests have been broken into two tests in #14483 but not for Batch tests, are we going to apply the same improvement for batch mode tests ?

I don't think there's much of a reason to separate them, since unlike the streaming tests both Spark versions consistently pass tests (while in streaming, Spark 3 is much less flaky than Spark 2, for unknown reasons).