9ea2835eaa
Ideally, we want to make CircleCI a "fast" test environment, with short feedback loop (~5mn). We are still far from this goal. This patch starts this process by removing "long" tasks which are non-essential and redundant with travisCI. It also acknowledges that parallelism is broken. The script should be more heavily updated to support parallelism, which might be important to support its goal.
76 lines
4.9 KiB
YAML
76 lines
4.9 KiB
YAML
# This configuration was automatically generated from a CircleCI 1.0 config.
|
|
# It should include any build commands you had along with commands that CircleCI
|
|
# inferred from your project structure. We strongly recommend you read all the
|
|
# comments in this file to understand the structure of CircleCI 2.0, as the idiom
|
|
# for configuration has changed substantially in 2.0 to allow arbitrary jobs rather
|
|
# than the prescribed lifecycle of 1.0. In general, we recommend using this generated
|
|
# configuration as a reference rather than using it in production, though in most
|
|
# cases it should duplicate the execution of your original 1.0 config.
|
|
version: 2
|
|
jobs:
|
|
build:
|
|
working_directory: ~/lz4/lz4
|
|
# Parallelism is broken in this file : it just plays the same tests twice.
|
|
# The script will have to be modified to support parallelism properly
|
|
# In the meantime, set it to 1.
|
|
parallelism: 1
|
|
shell: /bin/bash --login
|
|
# CircleCI 2.0 does not support environment variables that refer to each other the same way as 1.0 did.
|
|
# If any of these refer to each other, rewrite them so that they don't or see https://circleci.com/docs/2.0/env-vars/#interpolating-environment-variables-to-set-other-environment-variables .
|
|
environment:
|
|
CIRCLE_ARTIFACTS: /tmp/circleci-artifacts
|
|
CIRCLE_TEST_REPORTS: /tmp/circleci-test-results
|
|
# In CircleCI 1.0 we used a pre-configured image with a large number of languages and other packages.
|
|
# In CircleCI 2.0 you can now specify your own image, or use one of our pre-configured images.
|
|
# The following configuration line tells CircleCI to use the specified docker image as the runtime environment for you job.
|
|
# We have selected a pre-built image that mirrors the build environment we use on
|
|
# the 1.0 platform, but we recommend you choose an image more tailored to the needs
|
|
# of each job. For more information on choosing an image (or alternatively using a
|
|
# VM instead of a container) see https://circleci.com/docs/2.0/executor-types/
|
|
# To see the list of pre-built images that CircleCI provides for most common languages see
|
|
# https://circleci.com/docs/2.0/circleci-images/
|
|
docker:
|
|
- image: fbopensource/lz4-circleci-primary:0.0.4
|
|
steps:
|
|
# Machine Setup
|
|
# If you break your build into multiple jobs with workflows, you will probably want to do the parts of this that are relevant in each
|
|
# The following `checkout` command checks out your code to your working directory. In 1.0 we did this implicitly. In 2.0 you can choose where in the course of a job your code should be checked out.
|
|
- checkout
|
|
# Prepare for artifact and test results collection equivalent to how it was done on 1.0.
|
|
# In many cases you can simplify this from what is generated here.
|
|
# 'See docs on artifact collection here https://circleci.com/docs/2.0/artifacts/'
|
|
- run: mkdir -p $CIRCLE_ARTIFACTS $CIRCLE_TEST_REPORTS
|
|
# Test
|
|
# This would typically be a build job when using workflows, possibly combined with build
|
|
# This is based on your 1.0 configuration file or project settings
|
|
- run: CFLAGS= make clangtest && make clean
|
|
- run: g++ -v; make gpptest && make clean
|
|
- run: gcc -v; g++ -v; make ctocpptest && make clean
|
|
- run: gcc-5 -v; CC=gcc-5 CFLAGS="-O2 -Werror" make check && make clean
|
|
- run: gcc-5 -v; CC=gcc-5 CFLAGS="-O2 -m32 -Werror" CPPFLAGS=-I/usr/include/x86_64-linux-gnu make check && make clean
|
|
- run: gcc-6 -v; CC=gcc-6 MOREFLAGS="-O2 -Werror" make check && make clean
|
|
- run: make cmake && make clean
|
|
- run: make -C tests test-lz4
|
|
- run: make -C tests test-lz4c
|
|
- run: make -C tests test-frametest
|
|
- run: make -C tests test-fuzzer && make clean
|
|
- run: make -C lib all && make clean
|
|
- run: pyenv global 3.4.4; make versionsTest MOREFLAGS=-I/usr/include/x86_64-linux-gnu && make clean
|
|
- run: make travis-install && make clean
|
|
- run: gcc -v; CFLAGS="-O2 -m32 -Werror" CPPFLAGS=-I/usr/include/x86_64-linux-gnu make check && make clean
|
|
- run: clang -v; make staticAnalyze && make clean
|
|
- run: make platformTest CC=powerpc-linux-gnu-gcc QEMU_SYS=qemu-ppc-static && make clean
|
|
- run: make platformTest CC=powerpc-linux-gnu-gcc QEMU_SYS=qemu-ppc64-static MOREFLAGS=-m64 && make clean
|
|
- run: make platformTest CC=arm-linux-gnueabi-gcc QEMU_SYS=qemu-arm-static && make clean
|
|
- run: make platformTest CC=aarch64-linux-gnu-gcc QEMU_SYS=qemu-aarch64-static && make clean
|
|
# Teardown
|
|
# If you break your build into multiple jobs with workflows, you will probably want to do the parts of this that are relevant in each
|
|
# Save test results
|
|
- store_test_results:
|
|
path: /tmp/circleci-test-results
|
|
# Save artifacts
|
|
- store_artifacts:
|
|
path: /tmp/circleci-artifacts
|
|
- store_artifacts:
|
|
path: /tmp/circleci-test-results
|