Page History

...

It can be frustrating for developers to make changes that affect one part of the codebase (say documentation, or python) which then triggers trigger a full regression test of the entire codebase.  Ideally we could work backwards from code coverage reports and understand exactly which tests are required to ensure quality based on a given code change.  This is difficult in MXNet with it's its wide support of different languages.  However, it is likely that some basic heuristic would allow us cut back on tests in many cases.