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

**URL:** <https://chapel.discourse.group/t/chapel-ga-tests-2026-10-08/52096>\
**Category:** Nightly Testing\
**Created:** [October 8, 2026, 1:51pm UTC](https://chapel.discourse.group/t/chapel-ga-tests-2026-10-08/52096 "2026-10-08T13:51:28Z")\
**Posts on this page:** 4\
**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 8, 2026, 1:51pm UTC](https://chapel.discourse.group/t/chapel-ga-tests-2026-10-08/52096/1 "2026-10-08T13:51:28Z")

</div>

### The following GitHub Actions jobs failed:

- [full-checks / portability-tests-apptainer (debian-trixie-nollvm)](https://github.com/chapel-lang/chapel/actions/runs/37745689197/job/113206571488), step: "test Apptainer config debian-trixie-nollvm"

Ran 877 total jobs at commit 1c4bec31ae85249bd0f6569084209d5459b43066 "Also add a '.perftimeout' file for the SHOC Triad test (#29500)".

##### GitHub Actions run info:

- SHA: [1c4bec31ae85249bd0f6569084209d5459b43066](https://github.com/chapel-lang/chapel/commit/1c4bec31ae85249bd0f6569084209d5459b43066)
- Run ID: [37745689197](https://github.com/chapel-lang/chapel/actions/runs/37745689197)
- Run attempt: 1
- Run number: 62
- Triggering event name: schedule

---

<div class="post-metadata">

**Author:** ![bradcray](https://yyz2.discourse-cdn.com/free1/user_avatar/chapel.discourse.group/bradcray/32/72_2.png) [@bradcray](https://chapel.discourse.group/u/bradcray)\
**Post date:** [October 8, 2026, 9:57pm UTC](https://chapel.discourse.group/t/chapel-ga-tests-2026-10-08/52096/2 "2026-10-08T21:57:03Z")

</div>

I'm still learning how to read these nightly reports (potentially a good  
discussion/demo topic for a weekly meeting or deep-dive?). When I click  
into the failure on last night's run, the GitHub status icon is spinning  
as though it's still running, and there's no clear indication of what  
failed. Do others see the same thing?

Thanks,  
-Brad

---

<div class="post-metadata">

**Author:** ![annarift](https://yyz2.discourse-cdn.com/free1/user_avatar/chapel.discourse.group/annarift/32/656_2.png) [@annarift](https://chapel.discourse.group/u/annarift)\
**Post date:** [October 8, 2026, 10:12pm UTC](https://chapel.discourse.group/t/chapel-ga-tests-2026-10-08/52096/3 "2026-10-08T22:12:45Z")

</div>

Yes, I see that too, and I've seen it before. I believe that means GitHub did not properly "reap" the runner running this job.

I can't find the reference for it now, but I recall reading in GitHub Docs that a runaway runner can happen due to your job pegging the VM's CPU or using up all its RAM, since there is a small process in the VM that's responsible for reporting its state to GitHub. It could also be entirely GitHub's fault.

---

<div class="post-metadata">

**Author:** ![dal](https://yyz2.discourse-cdn.com/free1/user_avatar/chapel.discourse.group/dal/32/94_2.png) [@dal](https://chapel.discourse.group/u/dal)\
**Post date:** [October 8, 2026, 10:39pm UTC](https://chapel.discourse.group/t/chapel-ga-tests-2026-10-08/52096/4 "2026-10-08T22:39:37Z")

</div>

I see the same thing and wasn't sure what to make of it before I left for lunch. Thanks for the info, Anna!