Change Details

The current behavior is to read timing from the `timing.json` file location in the build directory is it exists. But this file is updated every time the functional test suite is run, which makes it impossible to predict which test will run as part of the `--extended` call and which one will run as part as a standard call. This diffs change this behavior so that the `timing.json` file from the source directory is always used as the timings source to determine which test to run.

The current behavior is to read timing from the `timing.json` file location in the build directory is it exists. But this file is updated every time the functional test suite is run, which makes it impossible to predict which test will run as part of the `--extended` call and which one will run as part as a standard call. This diffs change this behavior so that the `timing.json` file from the source directory is always used as the timings source to determine which test to run. Thanks @markblundeberg for reporting the issue.

The current behavior is to read timing from the `timing.json` file location in the build directory is it exists. But this file is updated every time the functional test suite is run, which makes it impossible to predict which test will run as part of the `--extended` call and which one will run as part as a standard call. This diffs change this behavior so that the `timing.json` file from the source directory is always used as the timings source to determine which test to run. Thanks @markblundeberg for reporting the issue.