Closed
Bug 1351321
Opened 7 years ago
Closed 6 years ago
Process to Identify `source.file.name` not in repo
Categories
(Testing :: Code Coverage, enhancement)
Testing
Code Coverage
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ekyle, Unassigned)
References
Details
For various reasons, the `source.file.name` coming out of local code coverage tools does not exist in the repository. For example, this can be because the code is copied to a common directory before compilation, or sources are auto-generated before compilation. The meta problem is figuring out what files can not be found in the repo, and a script should be made that will calculate this, ?on a daily basis?, for us. In the medium term we can use this script to identify specific problems to solve. In the long term this script can be used to ensure the system is consistent.
Comment 1•7 years ago
|
||
It should be possible to detect them by looking at the first directory of the path. If it is 'obj-firefox', it is a generated file.
Updated•7 years ago
|
Reporter | ||
Comment 2•6 years ago
|
||
This is fixed, or no longer an issue
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•