On 3/26/26 7:34 PM, Sebastiaan Couwenberg via Pkg-grass-devel wrote:
The CI pipeline for this change is failing repeatedly.
The build on i386 succeeds which suggests that we should skip
test_Sentinel1SarProduct more broadly to not get the test killed, on my local
system with more resources than Salsa CI the test succeeds.
I think we should skip it also when CI=true is set in the environment as done
by GitLab CI, or maybe even unconditionally.
What are your thoughts?
I've got a patch now that skips the test on 32-bit architectures or when less
than 8 GB memory is available.
The Salsa CI runners have less than 8, and the GitHub Actions runners have 16
GB total which explains why the test doesn't get killed there.
Kind Regards,
Bas
--
PGP Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
_______________________________________________
Pkg-grass-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel
