git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v2 0/2] travis-ci: run previously failed tests first, then slowest to fastest
@ 2016-01-26  9:53 larsxschneider
  2016-01-26  9:53 ` [PATCH v2 1/2] " larsxschneider
  2016-01-26  9:53 ` [PATCH v2 2/2] travis-ci: explicity use container-based infrastructure larsxschneider
  0 siblings, 2 replies; 4+ messages in thread
From: larsxschneider @ 2016-01-26  9:53 UTC (permalink / raw)
  To: git; +Cc: peff, gitster, mh, Lars Schneider

From: Lars Schneider <larsxschneider@gmail.com>

diff to v1:
    - improve the commit message ($gmane/284465)
    - rename the Travis cache directory from $HOME/.prove-cache to
      $HOME/travis-cache for clarity
    - explicitly use container-based infrastructure ($gmane/284432)

Thanks Mike, Jeff, and Junio for the review!

Cheers,
Lars

Lars Schneider (2):
  travis-ci: run previously failed tests first, then slowest to fastest
  travis-ci: explicity use container-based infrastructure

 .travis.yml | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

--
2.5.1

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [PATCH v2 1/2] travis-ci: run previously failed tests first, then slowest to fastest
  2016-01-26  9:53 [PATCH v2 0/2] travis-ci: run previously failed tests first, then slowest to fastest larsxschneider
@ 2016-01-26  9:53 ` larsxschneider
  2016-01-26 18:44   ` Junio C Hamano
  2016-01-26  9:53 ` [PATCH v2 2/2] travis-ci: explicity use container-based infrastructure larsxschneider
  1 sibling, 1 reply; 4+ messages in thread
From: larsxschneider @ 2016-01-26  9:53 UTC (permalink / raw)
  To: git; +Cc: peff, gitster, mh, Lars Schneider

From: Lars Schneider <larsxschneider@gmail.com>

The Travis-CI machines are in a clean state in the beginning of every run
(transient by default). Use the Travis-CI cache feature to make the prove
state persistent across consecutive Travis-CI runs on the same branch.
This allows to run previously failed tests first and run remaining tests
in slowest to fastest order. As a result it is less likely that Travis-CI
needs to wait for a single test at the end which speeds up the test suite
execution by ~2 min.

Travis-CI can only cache entire directories. Prove stores the .prove file
always in the t/ directory but we don't want to cache the entire t/ directory.
Therefore we create a symlink from $HOME/travis-cache/.prove to t/.prove and
cache the $HOME/travis-cache directory.

Unfortunately the cache feature is only available (for free) on the
Travis-CI Linux environment.

Suggested-by: Jeff King <peff@peff.net>
Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
---
 .travis.yml | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/.travis.yml b/.travis.yml
index c3bf9c6..610881e 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,5 +1,9 @@
 language: c
 
+cache:
+  directories:
+    - $HOME/travis-cache
+
 os:
   - linux
   - osx
@@ -18,7 +22,7 @@ env:
     - P4_VERSION="15.2"
     - GIT_LFS_VERSION="1.1.0"
     - DEFAULT_TEST_TARGET=prove
-    - GIT_PROVE_OPTS="--timer --jobs 3"
+    - GIT_PROVE_OPTS="--timer --jobs 3 --state=failed,slow,save"
     - GIT_TEST_OPTS="--verbose --tee"
     - CFLAGS="-g -O2 -Wall -Werror"
     - GIT_TEST_CLONE_2GB=YesPlease
@@ -67,6 +71,8 @@ before_install:
     p4 -V | grep Rev.;
     echo "$(tput setaf 6)Git-LFS Version$(tput sgr0)";
     git-lfs version;
+    mkdir -p $HOME/travis-cache;
+    ln -s $HOME/travis-cache/.prove t/.prove;
 
 before_script: make --jobs=2
 
-- 
2.5.1

^ permalink raw reply related	[flat|nested] 4+ messages in thread

* [PATCH v2 2/2] travis-ci: explicity use container-based infrastructure
  2016-01-26  9:53 [PATCH v2 0/2] travis-ci: run previously failed tests first, then slowest to fastest larsxschneider
  2016-01-26  9:53 ` [PATCH v2 1/2] " larsxschneider
@ 2016-01-26  9:53 ` larsxschneider
  1 sibling, 0 replies; 4+ messages in thread
From: larsxschneider @ 2016-01-26  9:53 UTC (permalink / raw)
  To: git; +Cc: peff, gitster, mh, Lars Schneider

From: Lars Schneider <larsxschneider@gmail.com>

Set `sudo: false` to explicitly use the (faster) container-based
infrastructure for the Travis-CI Linux build.

More info:
https://docs.travis-ci.com/user/ci-environment/#Virtualization-environments

Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
---
 .travis.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.travis.yml b/.travis.yml
index 610881e..f8b73ec 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,5 +1,7 @@
 language: c
 
+sudo: false
+
 cache:
   directories:
     - $HOME/travis-cache
-- 
2.5.1

^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH v2 1/2] travis-ci: run previously failed tests first, then slowest to fastest
  2016-01-26  9:53 ` [PATCH v2 1/2] " larsxschneider
@ 2016-01-26 18:44   ` Junio C Hamano
  0 siblings, 0 replies; 4+ messages in thread
From: Junio C Hamano @ 2016-01-26 18:44 UTC (permalink / raw)
  To: larsxschneider; +Cc: git, peff, mh

larsxschneider@gmail.com writes:

> From: Lars Schneider <larsxschneider@gmail.com>
>
> The Travis-CI machines are in a clean state in the beginning of every run
> (transient by default). Use the Travis-CI cache feature to make the prove
> state persistent across consecutive Travis-CI runs on the same branch.
> This allows to run previously failed tests first and run remaining tests
> in slowest to fastest order. As a result it is less likely that Travis-CI
> needs to wait for a single test at the end which speeds up the test suite
> execution by ~2 min.
>
> Travis-CI can only cache entire directories. Prove stores the .prove file
> always in the t/ directory but we don't want to cache the entire t/ directory.
> Therefore we create a symlink from $HOME/travis-cache/.prove to t/.prove and
> cache the $HOME/travis-cache directory.
>
> Unfortunately the cache feature is only available (for free) on the
> Travis-CI Linux environment.

Thanks.  I wouldn't be confused with the above description like
before.

I see systems other than Linux listed in os: section; presumably our
$HOME would not persist and we wouldn't even have $HOME/travis-cache
directory when we run on them, so "mkdir -p" would be both necessary
and save to have whether the "cache" feature is available or not.
And the "ln -s" would be the same way--either we symlink to a file
that hasn't been born (either on a platform without "cache" feature,
or the first run on Linux) and that is perfectly fine.

And all the systems listed in os: section supports symlinks, so
the "mkdir -p && ln -s" is safe.

Looks sensible.  Thanks.

>
> Suggested-by: Jeff King <peff@peff.net>
> Signed-off-by: Lars Schneider <larsxschneider@gmail.com>
> ---
>  .travis.yml | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/.travis.yml b/.travis.yml
> index c3bf9c6..610881e 100644
> --- a/.travis.yml
> +++ b/.travis.yml
> @@ -1,5 +1,9 @@
>  language: c
>  
> +cache:
> +  directories:
> +    - $HOME/travis-cache
> +
>  os:
>    - linux
>    - osx
> @@ -18,7 +22,7 @@ env:
>      - P4_VERSION="15.2"
>      - GIT_LFS_VERSION="1.1.0"
>      - DEFAULT_TEST_TARGET=prove
> -    - GIT_PROVE_OPTS="--timer --jobs 3"
> +    - GIT_PROVE_OPTS="--timer --jobs 3 --state=failed,slow,save"
>      - GIT_TEST_OPTS="--verbose --tee"
>      - CFLAGS="-g -O2 -Wall -Werror"
>      - GIT_TEST_CLONE_2GB=YesPlease
> @@ -67,6 +71,8 @@ before_install:
>      p4 -V | grep Rev.;
>      echo "$(tput setaf 6)Git-LFS Version$(tput sgr0)";
>      git-lfs version;
> +    mkdir -p $HOME/travis-cache;
> +    ln -s $HOME/travis-cache/.prove t/.prove;
>  
>  before_script: make --jobs=2

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2016-01-26 18:44 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-26  9:53 [PATCH v2 0/2] travis-ci: run previously failed tests first, then slowest to fastest larsxschneider
2016-01-26  9:53 ` [PATCH v2 1/2] " larsxschneider
2016-01-26 18:44   ` Junio C Hamano
2016-01-26  9:53 ` [PATCH v2 2/2] travis-ci: explicity use container-based infrastructure larsxschneider

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).