Create utils/full-rules-test.sh

[cschanaj]

it will somehow introduce false result, see #11560 should not be merged before #11998

ping @Hainish

[cowlicks]

How is this file run? How does $GIT_DIR get set? Using something like git rev-parse --show-toplevel) to get the toplevel might make it easier to run this file since it won't depend of mysterious global variables.

[cschanaj]

I run this by calling ./utils/full-rules-test.sh in the root directory. It is taken from

https-everywhere/test/rules.sh

Line 7 in 27f6f23

# Get to the repo root directory, even when we're symlinked as a hook.

and honestly I do not know where does this variable come from 😄

[cowlicks]

@cschanaj could you please describe the purpose of this PR? It isn't clear to me from the description.

[cschanaj]

Currently, we use a whitelist (utils/ruleset-whitelist.csv) to exempt a number of ruleset from Travis test. For some reasons, there are false entries, i.e. we are whitelisting some ruleset unnecessarily (as they can pass the Travis without error). This script will remove false whitelisting for rules-test.

[Hainish]

@cowlicks for additional context, any ruleset PR will run the fetch test on only the targets listed in that PR.

A more comprehensive full-fetch-test is something we periodically run, which

1. re-enables all rulesets that have been previously disabled due to fetch test failures
2. tests all enabled rulesets with the fetch test
3. disables all rulesets which fail the fetch test

Here's the code: https://github.com/EFForg/https-everywhere-full-fetch-test

This is done as a batch job, and was run last on Jun 20.