after unsuccessfully trying to find the correct path for my repository, I give up. I am looking for help to figure out the correct path fix for my mono repository.
Description of the issue
The coverage report uploaded from the original repository only contains data for the application layer. The data for infrastructure, domain, and presentation layer is missing. When inspected locally the data is complete.
The issue is finding the correct path fix for my case. I have created a new repository and added one of the packages to the new repo. For this new repo the coverage report is uploaded without missing as expected. Due to the purpose of the original repository that contains multiple packages, I would like to make it work with the nested root.
Since the repository is public, the codecov.yml, the codecov output and more information can be found inside the repository’s logs etc.
I have tried to create a new repository and copied the flutter_bloc example in the new repository. The codecov action works as intended and the report is complete. Therefore I assume, that I need to fix the path since the original repository contains 2 different examples. This means, that the repository root is 1 level above the coverage report containing example.
Hi @tom, it did not work with your latest suggestion.
With my original implementation without path fixing the root folder on my dashboard at codecov for the repository are as follows: flutter_bloc/lib/application
With the latest path fix of
fixes:
- ‘::flutter_bloc/’
The root folder is changed to flutter_bloc/flutter_bloc/lib/application
In the standalone repository that I’ve created for the flutter_bloc example, the files have the root folder of lib, which contains all test data.
On a side note, I only have tests and a coverage report in the subdirectory flutter_bloc
Hi @eddiesTime, as you saw I messed around with getting path fixing to work here to no avail. I’m not worried about the package size because (1) we gzip the report before uploading to Codecov, thus the small size, and (2) it seems like the report when we receive it has coverage for other files that aren’t showing up.
I’m going to escalate to the product team to see why this might be happening.
Hi @eddiesTime, I wanted you to be unblocked by this while we try to dig into a fix. You can see reports here which updates the coverage report like so. Let me know if this fixes your issue for now.