From 2f8283f01d24fce207e4099721f451a18dea60e1 Mon Sep 17 00:00:00 2001 From: Michael Stapelberg Date: Mon, 25 Jul 2011 15:53:33 +0200 Subject: [PATCH] add blog post: parallel test suite --- .../2011-07-25-parallel-test-suite.markdown | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 _posts/2011-07-25-parallel-test-suite.markdown diff --git a/_posts/2011-07-25-parallel-test-suite.markdown b/_posts/2011-07-25-parallel-test-suite.markdown new file mode 100644 index 0000000..d006d73 --- /dev/null +++ b/_posts/2011-07-25-parallel-test-suite.markdown @@ -0,0 +1,28 @@ +--- +date: 2011/07/25 15:53:00 +title: "parallel test suite" +--- + +As you may know, i3 v4.0 has a big test suite (currently 642 tests in 72 +files). As the test suite grew over time, the time needed to run all tests has +increased. While we want to spend some time on removing the delays in the tests +by properly checking if the X11 events have been processed, there also is an +easier solution for now: Running the tests in parallel. + +I just pushed +the commit to make our run script, complete-run.pl, do exactly that. + +Have a look at the time which was necessary to run a test before this commit: + + All tests successful. + Files=72, Tests=642, 139 wallclock secs (135.87 usr 0.47 sys + 34.86 cusr 3.12 csys = 174.32 CPU) + Result: PASS + +…and after this commit: + + All tests successful. + Files=72, Tests=642, 48 wallclock secs ( 0.28 usr 0.40 sys + 37.04 cusr 3.37 csys = 41.09 CPU) + Result: PASS + +48 seconds vs. 139 seconds is a pretty impressive speed-up :). -- 2.39.5