[BEAM-8454] Increase timeout and also enable thread stuckness detector.

[lukecwik]

I believe the timeout isn't high enough since on a more powerful machine this test takes almost 3 seconds to run so on a busy jenkins executor it might take longer. Regardless try to use the thread stuckness detector to get more information.

---

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.

Post-Commit Tests Status (on master branch)

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

Pre-Commit Tests Status (on master branch)

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

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

[lukecwik]

R: @apilloud

[lukecwik]

I ran the test 10000 times in a loop without a repro.

[apilloud]

LGTM.

You might look into cpulimit if this comes up again. I've found it really useful for adjusting timeouts that are occasionally triggered on shared testing infrastructure.

[lukecwik]

LGTM.

You might look into cpulimit if this comes up again. I've found it really useful for adjusting timeouts that are occasionally triggered on shared testing infrastructure.

Thanks for the suggestion.