You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Why is autotools.io in ruleset-coverage-whitelist.txt? #9627
The issue is that the hash of the current file matches the hash listed in the whitelist so it won't be remove by ruleset-coverage-whitelist-cleanup.sh.
The same thing holds true for www.mint.com. The ruleset Mint.xml looks fine to me, yet it is listed Here which has the same hash.
Reading through 0d5c34f, I am a little bit confused. Does the following mean that all the ruleset exist prior to 2014-02-12 are added to the white-list? That is, if a ruleset hasn't been updated after that, its entry will always residue in the white-list.
Instead, we create a list of SHA256 hashes of files as they stood on 2014-02-12 (plus some extras that slipped through because the changes were made before then but merged later). When running coverage tests, and files that match those hashes are ignored.
Activity
cschanaj commentedon Apr 23, 2017
The same thing holds true for
www.mint.com. The ruleset Mint.xml looks fine to me, yet it is listed Here which has the same hash.Reading through 0d5c34f, I am a little bit confused. Does the following mean that
all the ruleset exist prior to 2014-02-12 are added to the white-list? That is, if a ruleset hasn't been updated after that, its entry will always residue in the white-list.J0WI commentedon May 11, 2017
We didn't have any tests in 2014, so all existing rules have been white listed.
Bisaloo commentedon May 17, 2017
Thank you @J0WI. Could you tag this as question please? In case someone happens to have the same question.