Mario1159/verilator
1
0
Fork 0
forked from github/verilator
Code Pull Requests Releases 1 Activity
7e1980af7a
verilator/ci/ci-ccache-maint.bash

30 lines
917 B
Bash
Raw Normal View History

Travis: Use workspaces and per job persistent ccache (#2399) Change the Travis builds to use workspaces and persistent ccache We proceed in 2 stages (as before, but using workspaces for persistence): 1. In the 'build' stage, we clone the repo, build it and save the whole checkout ($TRAVIS_BUILD_DIR) as a workspace 2. In the 'test' stage, rather than cloning the repo, multiple jobs pull down the same workspace we built to run the tests from This enables: - Reuse of the build in multiple test jobs (this is what we used the Travis cache for before) - Each job having a separate persistent Travis cache, which now only contains the ccache. This means all jobs, including 'build' and 'test' jobs can make maximum use of ccache across runs. This drastically cuts down build times when the ccache hits, which is very often the case for 'test' jobs. Also, the separate caches only store the objects build by the particular job that owns the cache, so we can keep the per job ccache small. If the commit message contains '[travis ccache clear]', the ccache will be cleared at the beginning of the build. This can be used to test build complete within the 50 minute timeout imposed by Travis, even without a persistent ccache.
2020-06-03 20:10:13 +00:00
#!/usr/bin/env bash
Add the initial version of CI using GitHub Actions (#2665) * Add the initial version of CI using GitHub Actions * Update .github/workflows/check_pr.yml Co-authored-by: Wilson Snyder <wsnyder@wsnyder.org> * remove setting for travis * rename travis-*.bash to ci-*.bash * Rename TRAVIS_ variables to CI_ * install ccache and libsystemc(-dev) in ci-install.bash * Use CI_ variables and Ubuntu-20.04 that provides SystemC * call ccache maintenance Co-authored-by: Wilson Snyder <wsnyder@wsnyder.org>
2020-12-04 15:30:46 +00:00
# DESCRIPTION: Verilator: CI ccache maintenance
Travis: Use workspaces and per job persistent ccache (#2399) Change the Travis builds to use workspaces and persistent ccache We proceed in 2 stages (as before, but using workspaces for persistence): 1. In the 'build' stage, we clone the repo, build it and save the whole checkout ($TRAVIS_BUILD_DIR) as a workspace 2. In the 'test' stage, rather than cloning the repo, multiple jobs pull down the same workspace we built to run the tests from This enables: - Reuse of the build in multiple test jobs (this is what we used the Travis cache for before) - Each job having a separate persistent Travis cache, which now only contains the ccache. This means all jobs, including 'build' and 'test' jobs can make maximum use of ccache across runs. This drastically cuts down build times when the ccache hits, which is very often the case for 'test' jobs. Also, the separate caches only store the objects build by the particular job that owns the cache, so we can keep the per job ccache small. If the commit message contains '[travis ccache clear]', the ccache will be cleared at the beginning of the build. This can be used to test build complete within the 50 minute timeout imposed by Travis, even without a persistent ccache.
2020-06-03 20:10:13 +00:00
#
# Copyright 2020 by Geza Lore. This program is free software; you
# can redistribute it and/or modify it under the terms of either the GNU
# Lesser General Public License Version 3 or the Perl Artistic License
# Version 2.0.
#
# SPDX-License-Identifier: LGPL-3.0-only OR Artistic-2.0
################################################################################
# This script is run in 'before_script', once ccache has been set up.
################################################################################
set -e
set -x
# Show version
ccache --version
# Flush ccache if requested in commit message
Use both gcc and clang in CI (#2667) * Remove remaining TRAVIS_ variable * Use both gcc and clang.
2020-12-05 03:36:04 +00:00
COMMIT="${CI_PULL_REQUEST_SHA:-$CI_COMMIT}"
Add the initial version of CI using GitHub Actions (#2665) * Add the initial version of CI using GitHub Actions * Update .github/workflows/check_pr.yml Co-authored-by: Wilson Snyder <wsnyder@wsnyder.org> * remove setting for travis * rename travis-*.bash to ci-*.bash * Rename TRAVIS_ variables to CI_ * install ccache and libsystemc(-dev) in ci-install.bash * Use CI_ variables and Ubuntu-20.04 that provides SystemC * call ccache maintenance Co-authored-by: Wilson Snyder <wsnyder@wsnyder.org>
2020-12-04 15:30:46 +00:00
if git log --format=%B -n 1 "$COMMIT" | grep -q -i '\[CI\s\+ccache\s\+clear\]'; then
Travis: Use workspaces and per job persistent ccache (#2399) Change the Travis builds to use workspaces and persistent ccache We proceed in 2 stages (as before, but using workspaces for persistence): 1. In the 'build' stage, we clone the repo, build it and save the whole checkout ($TRAVIS_BUILD_DIR) as a workspace 2. In the 'test' stage, rather than cloning the repo, multiple jobs pull down the same workspace we built to run the tests from This enables: - Reuse of the build in multiple test jobs (this is what we used the Travis cache for before) - Each job having a separate persistent Travis cache, which now only contains the ccache. This means all jobs, including 'build' and 'test' jobs can make maximum use of ccache across runs. This drastically cuts down build times when the ccache hits, which is very often the case for 'test' jobs. Also, the separate caches only store the objects build by the particular job that owns the cache, so we can keep the per job ccache small. If the commit message contains '[travis ccache clear]', the ccache will be cleared at the beginning of the build. This can be used to test build complete within the 50 minute timeout imposed by Travis, even without a persistent ccache.
2020-06-03 20:10:13 +00:00
echo "Flushing ccache due to commit message"
ccache -C
fi
# Dump stats, then zero stats
ccache -s -z
Copy Permalink