[PATCH 3 of 3] test-progress: disable mocking-time tests on chg

[Jun Wu]

On 04/13/2016 07:42 AM, Pierre-Yves David wrote:
> Actually, not entirely. If fixing all extensions immediatly is too much a
> trouble we could have the devel warning disabled, either by default or for
> specific tests. Fixing them iteratively after than.

How about other issues?

1. Hacking stdlib is ugly
2. chg will only display devel-warn in extensions.loadall once (i.e. a second
run won't display these warnings)
3. Implementing the devel-warn itself require large refactoring if "import
chgserver" in extensions.py is not allowed.


> This would avoid implementing the feature twice, once in the script, and
> once for the markers. It also increase the chance that we actually end up
> with a devel warning.

There are too many tests related so only disabling by default makes sense.
If it is disabled by default then we lose the meaning of having it: prevent
new code from breaking chg.