# \[Chapel Merge\] Remove out-dated timeout for test

**URL:** <https://chapel.discourse.group/t/chapel-merge-remove-out-dated-timeout-for-test/52191>\
**Category:** Commits\
**Created:** [October 20, 2026, 4:27pm UTC](https://chapel.discourse.group/t/chapel-merge-remove-out-dated-timeout-for-test/52191 "2026-10-20T16:27:53Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![chapelhpcBot](https://avatars.discourse-cdn.com/v4/letter/c/7feea3/32.png) [@chapelhpcBot](https://chapel.discourse.group/u/chapelhpcBot)\
**Post date:** [October 20, 2026, 4:27pm UTC](https://chapel.discourse.group/t/chapel-merge-remove-out-dated-timeout-for-test/52191/1 "2026-10-20T16:27:53Z")

</div>

Branch: remove-timeout  
Revision: 0f533cbb572e8356972d65609e77811d17f4e237  
Author: jabraham17  
Link: [Remove out-dated timeout for test by jabraham17 · Pull Request #29549 · chapel-lang/chapel · GitHub](https://github.com/chapel-lang/chapel/pull/29549)  
Log Message:  
Remove out-dated timeout for test

Removes an out-dated timeout for a test.

The timeout was added when this test was a future and could fail/hang in certain conditions. But after [Fix issues with 'in'-intents when copying changes type by DanilaFe · Pull Request #27923 · chapel-lang/chapel · GitHub](https://github.com/chapel-lang/chapel/pull/27923) fixed this that is no longer the case. Such a short timeout means the test is frequently at risk of sporadically failing, which has been happening often in nightly testing

[Not reviewed - trivial]

Compare: [Remove out-dated timeout for test by jabraham17 · Pull Request #29549 · chapel-lang/chapel · GitHub](https://github.com/chapel-lang/chapel/pull/29549/changes)

Diff:  
D test/studies/shootout/reverse-complement/bradc/revcomp-blc-begin-ref.timeout  
[https://github.com/chapel-lang/chapel/pull/29549.diff](https://github.com/chapel-lang/chapel/pull/29549.diff)
