summaryrefslogtreecommitdiffstats
path: root/Tests/CommandLength
Commit message (Collapse)AuthorAgeFilesLines
* Merge topic 'ci-test-CommandLength'Brad King2024-02-161-1/+4
|\ | | | | | | | | | | | | | | edb833d69e Tests/CommandLength: Refactor test commands to reduce test run time Acked-by: Kitware Robot <kwrobot@kitware.com> Acked-by: buildbot <buildbot@kitware.com> Merge-request: !9256
| * Tests/CommandLength: Refactor test commands to reduce test run timeBrad King2024-02-151-1/+4
| | | | | | | | | | | | | | Since 2024-02-09 or so this test frequently times out on a few of our Windows CI runners. Use fewer but longer command lines to achieve a similar total command length. By running fewer commands, the test takes much less time.
* | Tests: Fix clang -Wstrict-prototypes warningsBrad King2023-10-261-1/+1
|/
* Ninja: Generate scripts for long custom command sequencesRoger Leigh2018-02-062-0/+21
Ninja runs just one command line for every build statement, so the Ninja generator needs to `&&`-chain multiple commands together into one long string. For long custom command sequences this can exceed the maximum command-line length for the operating system. In such cases, write the commands out to a script instead, and then run the script from Ninja's one command line. Co-Author: Brad King <brad.king@kitware.com> Fixes: #15612