check_254 "Core" failing during "M2 --check 2" on i386

This has happened twice so far (here and here) on continuous integration tests of the 1.17.1 package in Debian unstable for i386:

 -- capturing check(252, "Core")                                             -- 0.21414 seconds elapsed
 -- capturing check(253, "Core")                                             -- 3.12982 seconds elapsed
 -- capturing check(254, "Core")                                            

 *** out of memory trying to allocate 10000 bytes, exiting ***

 cd /tmp/M2-2214-0/1-rundir/; GC_MAXIMUM_HEAP_SIZE=400M "/usr/bin/M2-binary" -q --int --no-randomize --no-readline --silent --stop --print-width 129 <"/tmp/M2-2214-0/0.m2" >>"/tmp/M2-2214-0/0.tmp"
/tmp/M2-2214-0/0.tmp:0:1: (output file) error: Macaulay2 exited with status code 1
/tmp/M2-2214-0/0.m2:0:1: (input file)
M2: *** Error 1

It doesn't appear to be a problem when just running the test by itself, so I think it's probably just a result of having just run 254 other tests right before it! From an i386 chroot:

i1 : check_254 "Core"
 -- capturing check(254, "Core")                                             -- 0.000356972 seconds elapsed

Start with the Debian i386 logs and reproduce the full check sequence leading to check_254 "Core"; the issue says the test passes when run alone. Compare memory behavior across checks, including the shown GC_MAXIMUM_HEAP_SIZE=400M invocation. Done means the relevant i386 continuous-integration run completes without the out-of-memory failure.