-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Git] Data mismatch for lines of code added/removed for a release commit #659
Comments
Hi @linonymous, thank you for reporting this issue! Context I don't understand why you are then referencing a different commit of another repo, can you clarify it?
Analysis
However the GitHub interface for that commit (pndaproject/platform-salt@c305399) reports different data. In particular, one more file: I executed Perceval on that repo and the number of files returned is 70 for that commit (see command below). Thus, the problem may be in Perceval (which is the tool in charge of the collection phase).
I compared the file names returned by Perceval with the one listed in the GitHub UI and the missing file is I'm transfering the issue to the Perceval tracker. |
Under the hood Perceval runs the following Git command to inspect the log history:
The content retrieved for the commit
The JSON generated for that commit is:
Analysis
Summary
The second time the entry contains this data:
The information loss in Perceval occurs in the method
|
@valeriocos Thanks a lot for this in-depth RCA! As per my understanding, for commits with renamed files will suffer loss of data? |
You're welcome @linonymous ! We should run more tests, but I would say that the data loss occurs when the same file appears twice in the commit (e.g., a modification on the old file and rename) |
We have two problems here:
|
Issue:
The lines of code added and removed do not match with the exact commit data on github.
Command:
Data for a commit (JSON)
Actual Data:
Expected Data:
For the following commit:
pndaproject/platform-salt@c305399
lines_added : 3085
lines_removed: 188
This is specifically, as you can see is a tagged release commit. Do these commits are processed in a different way than rest? and 40+ error per commit constitutes for large errors after aggregation.
The text was updated successfully, but these errors were encountered: