start_progress() expects the total number as an uint64_t, that's Use values that don't fit into an int anyway. Parse-options expects in the tests of the progress output we won't Via parse-options's OPT_INTEGER into a uint64_t variable , so the The reason for that bogus value is that '-total's parameter is parsed + test-tool progress -total=3 Working hard total=' fail on big-endian systems, e.g. like this: In 't0500-progress-display.sh' all tests running 'test-tool progress Test-progress: fix test failures on big-endian systems Signed-off-by: Johannes Schindelin Signed-off-by: Junio C Hamano
Mistake on this developer's part, it was never turned on in the CI/PRīuilds. This results in 2x-3x longer run times of the test phase. This helper even knows how to run the tests in parallel, but due to a `prove`): we simply implemented a new test helper to run the test suite. Visual Studio uses `MSBuild`, or at least something very similar).ĭuring that transition, we needed to implement a new way to run the test `master`), however, this was changed to generate Visual Studio projectįiles and build the binaries using `MSBuild`, as this reflects moreĪccurately how Visual Studio users would want to build Git (internally, Later (but still before the patches made their way into git.git's Were implemented imitating `linux-clang`, i.e. still using the Originally, the CI/PR builds that build and test using Visual Studio Ci(visual-studio): actually run the tests in parallel
0 kommentar(er)
