Compilation error if the user does not own the code files

The underlying BEAM code (on Unix-ish systems, anyways) always calls utime with a not-NULL pointer:

but that’s been in the code for years and years, so it can’t be the reason for the recent change in behavior you observed.

The name of the function that’s calling touch (each_cycle) suggests that something may have changed in the dependency graph of your application. Comparing the output of mix xref between an older “known good” version and now could provide some insight.

but that’s been in the code for years and years, so it can’t be the reason for the recent change in behavior you observed.

No, I didn’t mean that some behavior changed in touch or somewhere else outside my code. My question was that, according to the each_cycle function comment (if I understood correctly), some changes may be happening. But what kind of changes exactly? Are we talking about some files already compiled and some need to be updated? Why haven’t I encountered this error before? Why should the compiler execute `File.touch(“my_file.ex”, timestamp)? What changes caused this behavior?

The name of the function that’s calling touch (each_cycle) suggests that something may have changed in the dependency graph of your application. Comparing the output of mix xref between an older “known good” version and now could provide some insight.

The problem is also that the specific file that causes the error has not changed from version to version. This module was imported 4 times in an old working version. In the new version it is imported 5 times. I don’t see this as a problem and have no idea what could be wrong.

Hard to say with the info you’ve given, maybe the CI containers have gotten some upgrades that contributed to the problem? But as @al2o3cr said, your best bet is to try to have a before/after output of mix xref and compare.