In Cairo coverage, we utilize compilator mappings in the form:
Sierra ID -> list of details
where each detail is a triple representing:
Path to file
Line in file
Function name
Currently, we determine if a file belongs to the user project by excluding files that point to the Scarb cache. This method is unreliable as users can specify different locations for the cache via the SCARB_CACHE environment variable, and cache locations vary across different operating systems.
To fix this, we should:
Implement a heuristic to get the location of the user project through the source_sierra_path in the call trace
In Cairo coverage, we utilize compilator mappings in the form:
where each detail is a triple representing:
Currently, we determine if a file belongs to the user project by excluding files that point to the Scarb cache. This method is unreliable as users can specify different locations for the cache via the
SCARB_CACHEenvironment variable, and cache locations vary across different operating systems.To fix this, we should:
source_sierra_pathin the call trace