# \[Chapel GA Tests\] 2026-10-20

**URL:** <https://chapel.discourse.group/t/chapel-ga-tests-2026-10-20/52189>\
**Category:** Nightly Testing\
**Created:** [October 20, 2026, 11:10am UTC](https://chapel.discourse.group/t/chapel-ga-tests-2026-10-20/52189 "2026-10-20T11:10:59Z")\
**Posts on this page:** 2\
**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, 11:10am UTC](https://chapel.discourse.group/t/chapel-ga-tests-2026-10-20/52189/1 "2026-10-20T11:10:59Z")

</div>

### The following GitHub Actions jobs failed:

- [full-checks / Chapel paratest with AddressSanitizer / Aggregate results (asan)](https://github.com/chapel-lang/chapel/actions/runs/39388118860/job/118594797144), step: "aggregate and report results"

Ran 983 total jobs at commit 29d44f187634325666cb0a9c420c7d1cf334e609 "Build an arm version of the CI docker container (#29535)".

##### GitHub Actions run info:

- SHA: [29d44f187634325666cb0a9c420c7d1cf334e609](https://github.com/chapel-lang/chapel/commit/29d44f187634325666cb0a9c420c7d1cf334e609)
- Run ID: [39388118860](https://github.com/chapel-lang/chapel/actions/runs/39388118860)
- Run attempt: 1
- Run number: 81
- Triggering event name: schedule

---

<div class="post-metadata">

**Author:** ![jabraham](https://yyz2.discourse-cdn.com/free1/user_avatar/chapel.discourse.group/jabraham/32/430_2.png) [@jabraham](https://chapel.discourse.group/u/jabraham)\
**Post date:** [October 20, 2026, 4:25pm UTC](https://chapel.discourse.group/t/chapel-ga-tests-2026-10-20/52189/2 "2026-10-20T16:25:09Z")

</div>

This test has been timing out. A lot. Turns out, its probably because of a stale `.timeout` file in the repo. [Remove out-dated timeout for test by jabraham17 · Pull Request #29549 · chapel-lang/chapel · GitHub](https://github.com/chapel-lang/chapel/pull/29549) removes that, and hopefully we will see less of this sporadic.

-Jade