Open Fraa-124 opened 2 weeks ago
From some quick googling it looks like this means it received a SIGTERM signal from the outside (possibly, the container it is running in actually received this).
Did you try just restarting the job? It could have been a flake. If it is happening reliably it could be that the container is running out of memory, or timing out, something along those lines.
This issue is blocking our migration to Flutter 3.24.3. Our CI fails with only an exit code 143 and no additional details. But what does exit code 143 mean?
It compiles fine locally.
With the verbose flag enabled, no errors are thrown either, only [INFO] and [FINE] logs are shown.