Open hubertp opened 10 months ago
Related to #7775
Can we add a ls /runner/_work/enso/enso/distribution/lib/Standard/Base/0.0.0-dev/src/Data/
to the CI temporarily?
I'd really like to know if our files are in inconsistent state (that would be horribly weird; it would mean that there are some git checkout artifacts) OR if actually the files are not there and it is an issue of the missing file being referenced in some stale IR cache?
@mwu-tow Maybe we should by default purge all IR caches on checkout?
I think we should purge the following locations:
/runner/_work/enso/enso/built-distribution/*
$ENSO_DATA_DIRECTORY/cache/*
where ENSO_DATA_DIRECTORY
is a 'virtual' path that depends on the OS, as documented;
~/.local/share/enso/cache
%LocalAPPDATA%\enso\cache
Maybe let's try purging the mentioned directories when runner starts processing a new task, and we can see if the issue disappear or still persists?
I'd also like to see the results of the ls
for a few weeks on the CI, so that if the issue ever re-occurs we have some more 'debug' data to understand it (since it is so random, it is very hard to debug in any other way, I imagine)
Consider the failure in one of the recent PRs:
the problem is that
Enso_Cloud
is being introduced in a separate PR and is here expected because the runner checkout out the state from that PR. While there have been service register changes to support incremental compilation, they aren't addressing Enso files.