LAMA0076: Metalama can't write the crash report

Cause

When Metalama fails with an unexpected exception, it writes a crash report, a text file with the details of the exception, and reports the error LAMA0001 (or the warning LAMA0049 when the exception can be ignored) with the path of this file. See LAMA0001.

Metalama reports LAMA0076 when writing the crash report fails with an I/O error, for instance because the crash report directory can't be created, the disk is full, or the current user doesn't have write access to the directory. In this case, the message of LAMA0001 or LAMA0049 gives <error> instead of the path of the report, and LAMA0076 explains why. In the message, <ReportFailure> gives the path of the file that Metalama tried to write and the reason of the failure.

LAMA0076 itself is only a consequence: the actual problem is the unexpected exception reported at the same time.

This diagnostic depends on an unexpected exception in Metalama and on the file system of the machine, so it can't be shown in an example.

Resolution

1. Read the reason given in the message and fix the access to the crash report directory. By default, crash reports are written to %TEMP%\Metalama\CrashReports on Windows, and to the Temp/CrashReports subdirectory of the Metalama application data directory on Linux and macOS. Make sure that this directory exists or can be created, that the disk isn't full, and that the user running the build can write to it. On a build server, the account that runs the build often has a different temporary directory.
2. If you can't make the default directory writable, set the METALAMA_TEMP environment variable to a writable directory. Metalama then writes the crash reports to $METALAMA_TEMP/Metalama/CrashReports.
3. Build again, so that Metalama writes the crash report, and follow the resolution of LAMA0001.

See also

• LAMA0001
• LAMA0049
• How to file an issue