Skip to content

Handle malformed LZF back references #93

Handle malformed LZF back references

Handle malformed LZF back references #93

Workflow file for this run

name: Build
on:
push:
branches:
- master
paths-ignore:
- 'README.md'
- 'VERSION.txt'
pull_request:
branches:
- master
permissions:
contents: read
jobs:
build:
runs-on: 'ubuntu-latest'
strategy:
fail-fast: false
matrix:
java_version: ['8', '11', '17', '21']
env:
JAVA_OPTS: '-XX:+TieredCompilation -XX:TieredStopAtLevel=1'
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
- name: Set up JDK
uses: actions/setup-java@03ad4de0992f5dab5e18fcb136590ce7c4a0ac95 # v5.6.0
with:
distribution: 'temurin'
java-version: ${{ matrix.java_version }}
cache: 'maven'
- name: Build
run: ./mvnw -B -q -ff -ntp verify
- name: Generate code coverage
if: ${{ github.event_name != 'pull_request' && matrix.java_version == '8' }}
run: ./mvnw -B -q -ff -ntp test
- name: Publish code coverage
if: ${{ github.event_name != 'pull_request' && matrix.java_version == '8' }}
uses: codecov/codecov-action@fb8b3582c8e4def4969c97caa2f19720cb33a72f # v7.0.0
with:
token: ${{ secrets.CODECOV_TOKEN }}
files: ./target/site/jacoco/jacoco.xml
flags: unittests
# TODO: Maybe consider caching Jazzer `.cifuzz-corpus` directory if that improves fuzzing performance?
# But could become outdated when fuzz test methods are changed
fuzz:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
- name: Set up JDK
uses: actions/setup-java@03ad4de0992f5dab5e18fcb136590ce7c4a0ac95 # v5.6.0
with:
distribution: 'temurin'
java-version: 17
cache: 'maven'
- name: Run tests
id: fuzz-tests
# Don't run with `-q`, to see fuzzing progress
run: ./mvnw -B -ff -ntp --activate-profiles fuzz test
- name: Upload fuzz test inputs
if: always() && steps.fuzz-tests.outcome == 'failure'
uses: actions/upload-artifact@043fb46d1a93c77aae656e7c1c64a875d1fc6a0a # v7.0.1
with:
name: fuzz-test-inputs
path: src/test/resources/**/*Inputs/**