C
Branch: faster-comd Revision: 26e82316afcceb6dc5c8c5382a343020a3b06703 Author: bradcray Merged at: 2026-11-04T21:13:21Z Link: Dial down CoMD's nSteps for correctness testing by 10x by bradcray · Pull Request #29651 · chapel-lang/chapel · GitHub Log Message: Dial down CoMD's nSteps for correctness testing by 10x This test has been taking close to a half hour on Macs when run in oversubscribed mode. Here, I'm dialing its number of time steps down by 10x to make that a bit less ridiculous. Updated…
C
Branch: jade/run-ci-with-new-image Revision: d5f4fa127bc66a92c19d929606043163bd94ebdf Author: jabraham17 Merged at: 2026-11-04T21:13:20Z Link: Run entire CI with new CI images by jabraham17 · Pull Request #29636 · chapel-lang/chapel · GitHub Log Message: Run entire CI with new CI images Adjusts how new CI images are validated, now the entire CI must pass before a new CI image can make it onto main. Whenever build-CI-container is triggered, a build is pushed to the container registry tagged as…
C
Hello, veigelherne02: Here is what brave-origin browser's AI responded about remote editing: Yes, the TTT Editor can edit remote files. SSH Support: The editor is designed to run in the terminal, allowing it to work over SSH sessions where you are directly editing files on a remote server. Local vs. Remote: It does not use a protocol like SFTP to fetch files over the network; instead, it operates on files accessible within the terminal environment, meaning it edits files directly on the remote…
C
Branch: timeout-install Revision: 6d13e384fe3a11ff5911aa3ef56a6bfd48736891 Author: jabraham17 Merged at: 2026-11-04T20:34:56Z Link: Adds an explicit apt install timeout by jabraham17 · Pull Request #29650 · chapel-lang/chapel · GitHub Log Message: Adds an explicit apt install timeout Adds an explicit apt install timeout for gcc (which falls back to the cache) Motivated by Run PR checks · chapel-lang/chapel@d6c2e28 · GitHub, which won't trigger Acquire::http(s)::Timeout because there is still…
C
Thanks for that info, Jade — it's very helpful. Looks like this test has been running at nearly 30 minutes on Macs in oversubscribed mode with small numbers of cores, so I dialed down its number of time steps by 10x in Dial down CoMD's nSteps for correctness testing by 10x by bradcray · Pull Request #29651 · chapel-lang/chapel · GitHub to make it a bit more reasonable and further from the GASNet timeout for small core count systems. -Brad
C
Branch: perf-better-isel Revision: 4e9ef080be90528dc2c39ca8a37429f72d0aa9a8 Author: jabraham17 Merged at: 2026-11-04T19:43:18Z Link: Test faster llvm codegen in playground by jabraham17 · Pull Request #29649 · chapel-lang/chapel · GitHub Log Message: Test faster llvm codegen in playground Test Refactor LLVM codegen to result in faster backend ISEL by jabraham17 · Pull Request #29638 · chapel-lang/chapel · GitHub in perf playground [Not reviewed - trivial] Compare: Test faster llvm codegen in…
C
Branch: add-linuxbrew Revision: d6c2e287954ac76d2e69b86866a7698e07d918e3 Author: jabraham17 Merged at: 2026-11-04T19:43:17Z Link: Add CI for from-source builds with linuxbrew by jabraham17 · Pull Request #29647 · chapel-lang/chapel · GitHub Log Message: Add CI for from-source builds with linuxbrew Adds testing for building Chapel from source via linxubrew dependencies (like LLVM) [Reviewed by @arifthpe] Compare: Add CI for from-source builds with linuxbrew by jabraham17 · Pull Request #29647 ·…
C
Syntax highlighting for Chapel does seem thin on the ground, so it's good to hear about another option. I hadn't come across ttt before this post. Does it handle editing remotely, or is it strictly a local tool? I'm curious whether the highlighting covers the whole language or just the core keywords. Either way, having fewer hoops to jump through when reading Chapel code sounds useful.
C
Alex, the point about boundary conditions living outside the timed loop is the part that would trip up most people — it looks harmless precisely because it isn't where the performance work happens. A StencilDist tutorial built around that pitfall would be more useful than a compiler warning, since the fluff-region read semantics are the actual thing to internalize. The 3D workshop progression from C+MPI through BlockDist to StencilDist sounds like a compelling way to show the code-length gap.…
C
Branch: docker-release-check-version Revision: fcf26dce0b3b40c69e19daeef86e57255d4da4b1 Author: arifthpe Merged at: 2026-11-04T18:21:10Z Link: Add expected version check in release-docker workflow by arifthpe · Pull Request #29644 · chapel-lang/chapel · GitHub Log Message: Add expected version check in release-docker workflow Add a step to the release-docker.yml workflow which asserts the version printed by chpl --version in the to-be-released image matches the expected release version. Due to…
C
You can download the full start_test log by opening the "Aggregate ..." run of the job you are interested in, going to the "upload aggregate results", and downloading the archive. The easiest way to find previous runs is to click on the job link from the discourse email, the GA actions view is pretty poor and hard to navigate -Jade
C
Looking for some GA triage education here: This seems as though it could just be a timeout for a memory intensive test. Is there a best practice for stepping back in time within the GA nightly framework to see how long it took to run on previous nights? I started down the path of going back to the previous run, finding the gasnet.darwin aggregation jobs, but then am not sure how to zero in on the log segment that would cover the same test efficiently. Or is there a way to just jump to the raw…
C
The following GitHub Actions jobs failed: full-checks / Chapel paratest on darwin mulitilocale tests with gasnet (segment everything) / Aggregate results (gasnet.darwin), step: "aggregate and report results" 1 failed test(s) in gasnet.darwin: [Error: Timed out executing program studies/comd/elegant/arrayOfStructs/CoMD] Ran 885 total jobs at commit f88062e47d37229164441886964d79b4bbad8aa7 "Improve CHPL_COMM=gasnet debugger exit (#29645)". GitHub Actions run info: SHA:…
C
Branch: better-debugger-exit Revision: f88062e47d37229164441886964d79b4bbad8aa7 Author: jabraham17 Merged at: 2026-11-04T01:12:33Z Link: Improve CHPL_COMM=gasnet debugger exit by jabraham17 · Pull Request #29645 · chapel-lang/chapel · GitHub Log Message: Improve CHPL_COMM=gasnet debugger exit This PR attempts to improve the exit behavior of Chapel executable under --lldb with the gasnet comm layer. Since both the parent (original process) and child (lldb-server) are "gasnet processes" that…
C
Branch: prevent-core Revision: 99ca8e78d06331a3cc9ef9cafc070bd6f5746fb3 Author: jabraham17 Merged at: 2026-11-04T00:45:28Z Link: Prevent core files in ga-paratest by jabraham17 · Pull Request #29646 · chapel-lang/chapel · GitHub Log Message: Prevent core files in ga-paratest We've had a few tests fail in the CI (specifically the GASNet segment-fast tests) due to what looks to be the test running out of memory in strange ways. I traced this to a side effect of other tests crashing (either…
C
Branch: py-version-ccache Revision: f08e29057e6419f564faad386a5005a4b4663bb8 Author: benharsh Merged at: 2026-11-03T23:35:31Z Link: Better usage of ccache for python-version-tests by benharsh · Pull Request #29640 · chapel-lang/chapel · GitHub Log Message: Better usage of ccache for python-version-tests Use separate ccaches for 3.10-12 and 3.13-15, as the two groups built on different ubuntu versions. We should be able to get cache hits on the compiler objects, despite the different comm…
C
This is a bit nebulous of an issue, but I think this is a side effect of other tests (specifically twoLocales) crashing and brining down other tests in the runner. Prevent core files in ga-paratest by jabraham17 · Pull Request #29646 · chapel-lang/chapel · GitHub will hopefully prevent this side effect and Improve CHPL_COMM=gasnet debugger exit by jabraham17 · Pull Request #29645 · chapel-lang/chapel · GitHub should hopefully improve twoLocales crashes -Jade
C
Brad's read seems right that nobody following has tried it. I don't have the hardware myself, so I can't confirm anything firsthand. Given the 2027 official Linux support timeline, the practical question might be whether Chapel's build dependencies even compile cleanly on ARM64 with an immature kernel and toolchain. If someone does attempt it, the useful details would be which distro image, kernel version, and whether the LLVM backend builds without patches. Worth watching the distro's ARM64…
C
Branch: speedup-docker Revision: b41b04c89847b02994061b274e04b3a3c87215c0 Author: jabraham17 Merged at: 2026-11-03T22:52:00Z Link: Optimize docker builds by jabraham17 · Pull Request #29643 · chapel-lang/chapel · GitHub Log Message: Optimize docker builds Optimizes the docker builds to speedup builds and reduce pressure on other jobs stops caching, since we do COPY . . just about any meaningful change invalidates the cache, making the cache just take up valuable space use .dockerignore to avoid…
C
It probably won't change the printchplenv output, but it will mean clang++ is no longer broken It is possible to hit this problem on many platforms. If clang picks a GCC install to use that is missing libstdc++, you will encounter this problem. Newer versions of clang do a better job of warning in this case, and in the future I expect clang will become smarter about not picking these broken GCC installs -Jade
C
The distinction you drew between gcc and clang++ is what made this click for me, since I'd assumed the compiler question was mostly academic until Jade's test showed clang++ failing on its own. Worth noting that the version mismatch was specific to the Ubuntu 22 package, so anyone on a different distro or installing from source might hit something else entirely. Did the g++-12 install change any of your printchplenv output, or did it just resolve the verify error?
C
Branch: fix-gasnet-docker Revision: f5dec38ea74811216ef66ad5a090adf6393fe625 Author: jabraham17 Merged at: 2026-11-03T21:45:16Z Link: Fix docker image build working off of latest by jabraham17 · Pull Request #29641 · chapel-lang/chapel · GitHub Log Message: Fix docker image build working off of latest The nightly gasnet and gasnet-smp Docker images were being built on top of the published chapel/chapel:latest from Docker Hub instead of the base image built earlier in the same run.…
C
Hi Alex — Sounds good, best of luck with the workshop preparation. If you'd be interested in writing an article summarizing some of your versions and comparison for the Chapel blog, let us know. Stencils come up so freuqently that I imagine you'd be creating something that people would refer back to over time. -Brad
C
Hi Brad, Thank you for finding the mistake in my code and for the detailed explanation! This is a very subtle issue, yet unfortunately an easy one to introduce. Since the boundary conditions were outside the main timed loop, I naively assumed that setting them locally on node 0 would simply work, and never gave it a second thought. I doubt that user errors like this can be prevented at the compiler level, and should probably be addressed through user education. Perhaps we could put together a…
C
29642, "jabraham17", "[Bug]: Extern blocks insert symbols into scope", "2026-11-03T20:05:54Z" Open issue chapel-lang/chapel [Bug]: Extern blocks insert symbols into scope opened 08:05PM - 03 Nov 26 UTC jabraham17 type: Bug area: Compiler area: Language The following successfully compiles ``` extern { } var x: c_int = 0; writeln(x…); ``` This should get an error, that `c_int` is not defined. A correct program should `use CTypes`. The presence of an extern block seems to auto-import CTypes into…
C
Branch: dependabot/github_actions/zizmorcore/zizmor-action-0.7.1 Revision: 81ef7c00f6f8ceb50d7d24bbe4208ac7861767ad Author: arifthpe Merged at: 2026-11-03T19:57:05Z Link: Bump zizmorcore/zizmor-action from 0.6.4 to 0.7.1 by dependabot[bot] · Pull Request #29625 · chapel-lang/chapel · GitHub Log Message: Bump zizmorcore/zizmor-action from 0.6.4 to 0.7.1 Bumps zizmorcore/zizmor-action from 0.6.4 to 0.7.1. Release notes (click for more details) Commits (click for more details) Compare: Bump…
C
Branch: add-pic-paratest Revision: de95b8bdbf23ca3d2dff93c3dc4a9a0d02e302e0 Author: jabraham17 Merged at: 2026-11-03T18:50:38Z Link: Add LIB_PIC=pic paratest configs by jabraham17 · Pull Request #29622 · chapel-lang/chapel · GitHub Log Message: Add LIB_PIC=pic paratest configs Add nightly tests for CHPL_LIB_PIC=pic with both comm=none and comm=gasnet [Reviewed by @arifthpe] Compare: Add LIB_PIC=pic paratest configs by jabraham17 · Pull Request #29622 · chapel-lang/chapel · GitHub Diff: M…
C
Branch: check-old-python Revision: 26a24520763931792b1eff1b6c589daf695dcec5 Author: jabraham17 Merged at: 2026-11-03T18:19:47Z Link: add CI to check that basic python scripts will work with python 3.5 by jabraham17 · Pull Request #29590 · chapel-lang/chapel · GitHub Log Message: add CI to check that basic python scripts will work with python 3.5 Adds very basic CI to check that printchplenv will work with Python 3.5. Resolves https://github.com/Cray/chapel-private/issues/6105 Future work should…
C
Most of these failed with no output, except test1D2D which got: FATAL ERROR: Master got an xSocket: error in sendAll() - connection closed (32:Broken pipe)
C
The following GitHub Actions jobs failed: full-checks / Chapel paratest with GASNet fast segment / Aggregate results (gasnet-fast), step: "aggregate and report results" 4 failed test(s) in gasnet-fast: [Error matching program output for classes/lydia/overrides/remoteVersion] [Error matching program output for library/standard/Random/deitz/test1D2D] [Error matching program output for library/standard/Random/sample-block] [Error matching program output for l…