Closed kamalsaleh closed 6 months ago
Thank you very much. Could you please add the above example in an example file that covers the new code? Mabye you just forgot to git add
it :)
Done!
Attention: Patch coverage is 93.33333%
with 2 lines
in your changes are missing coverage. Please review.
Project coverage is 76.10%. Comparing base (
7f8760c
) to head (b518a1e
).
Files | Patch % | Lines |
---|---|---|
FpCategories/gap/PathCategories.gi | 92.85% | 2 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
The tests took an hour longer than usual. I will restart them. In case the regression remains I will ping you.
It seems there is a problem in uploading the code-coverage:
['error'] There was an error running the uploader: Error uploading to [https://codecov.io:](https://codecov.io/) Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}
[2024-04-11T10:18:31.615Z] ['verbose'] The error stack is: Error: Error uploading to [https://codecov.io:](https://codecov.io/) Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found')}
at main (/snapshot/repo/dist/src/index.js)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[2024-04-11T10:18:31.615Z] ['verbose'] End of uploader: 1060 milliseconds
Codecov upload failed, retrying in 60s
I will remove the current commit and try a phantom commit to see if my code somehow causes this issue.
Uploading the code-coverage fails many times (and eventually succeeds) as expected irrelevant of my commit. It looks like a Github issue and might be resolved after few days. I have understood from Fabian that uploading the code-coverage is enabled only on gap-docker-master for pull-requests or merges; and is disabled in the gap-docker and all nighty tests. The same behaviour has been happining for few days in CAP_Project. Hence, I will re-push the original commit. It might take time until tests pass but still it can then be merged.
Thanks for the commit and the investigation :)
Example:
Bump FpCategories to V2024.04-01