Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Add Github actions workflow #35

Merged
merged 5 commits into from
Sep 26, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 48 additions & 0 deletions .github/workflows/cmake-single-platform.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
# This starter workflow is for a CMake project running on a single platform. There is a different starter workflow if you need cross-platform coverage.
# See: https://github.com/actions/starter-workflows/blob/main/ci/cmake-multi-platform.yml
name: Basic Tests for BLISS Benchmark

on:
push:
branches:
- "main"
pull_request:
branches: [ "main" ]

env:
# Customize the CMake build type here (Release, Debug, RelWithDebInfo, etc.)
BUILD_TYPE: Release

jobs:
build:
# The CMake configure and build commands are platform agnostic and should work equally well on Windows or Mac.
# You can convert this to a matrix build if you need cross-platform coverage.
# See: https://docs.github.com/en/free-pro-team@latest/actions/learn-github-actions/managing-complex-workflows#using-a-build-matrix
runs-on: ubuntu-latest

steps:
- uses: actions/checkout@v4
with:
submodules: 'true'
token: ${{ secrets.ACTIONS_ACCESS_TOKEN }}

- name: Configure CMake
# Configure CMake in a 'build' subdirectory. `CMAKE_BUILD_TYPE` is only required if you are using a single-configuration generator such as make.
# See https://cmake.org/cmake/help/latest/variable/CMAKE_BUILD_TYPE.html?highlight=cmake_build_type
run: cmake -B ${{github.workspace}}/build -DCMAKE_BUILD_TYPE=${{env.BUILD_TYPE}}

- name: Build
# Build your program with the given configuration
run: cmake --build ${{github.workspace}}/build --config ${{env.BUILD_TYPE}}

- name: Verify Tests Exist

working-directory: ${{github.workspace}}/tests
run: sh unit_test_exists.sh

- name: Test
working-directory: ${{github.workspace}}/build
# Execute tests defined by the CMake configuration.
# See https://cmake.org/cmake/help/latest/manual/ctest.1.html for more detail
run: ctest -C ${{env.BUILD_TYPE}}

31 changes: 31 additions & 0 deletions tests/unit_test_exists.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@

# boolean flag to check if test passed
test_passed=true

# loop through all files in src/bliss directory excluding subdirectories
for file in $(find ../src/bliss -type f -name "bench_*.h"); do
# get the filename without the path
filename=$(basename $file)
# get the filename without the extension
filename_no_ext="${filename%.*}"
# get index name from filename which is of format bench_<index>.h
index=$(echo $filename_no_ext | cut -d'_' -f2)

# check if the test folder exists
if [ ! -d "test_$index" ]; then
echo "tests/test_$index/ directory does not exist"
test_passed=false
break
else
# check if test folder contains a CMakeLists.txt or <index>_tests.cpp file
if [ ! -f "test_$index/CMakeLists.txt" ] && [ ! -f "test_$index/${index}_tests.cpp" ]; then
echo "tests/test_$index/ directory does not contain CMakeLists.txt or ${index}_tests.cpp file"
test_passed=false
break
fi
fi
done

if [ "$test_passed" = true ]; then
echo "unit tests exist for all indexes"
fi