1# This configuration was automatically generated from a CircleCI 1.0 config.
2# It should include any build commands you had along with commands that CircleCI
3# inferred from your project structure. We strongly recommend you read all the
4# comments in this file to understand the structure of CircleCI 2.0, as the idiom
5# for configuration has changed substantially in 2.0 to allow arbitrary jobs rather
6# than the prescribed lifecycle of 1.0. In general, we recommend using this generated
7# configuration as a reference rather than using it in production, though in most
8# cases it should duplicate the execution of your original 1.0 config.
9version: 2
10jobs:
11  build:
12    working_directory: ~/lz4/lz4
13    parallelism: 1
14    shell: /bin/bash --login
15    # CircleCI 2.0 does not support environment variables that refer to each other the same way as 1.0 did.
16    # 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 .
17    environment:
18      CIRCLE_ARTIFACTS: /tmp/circleci-artifacts
19      CIRCLE_TEST_REPORTS: /tmp/circleci-test-results
20    # In CircleCI 1.0 we used a pre-configured image with a large number of languages and other packages.
21    # In CircleCI 2.0 you can now specify your own image, or use one of our pre-configured images.
22    # The following configuration line tells CircleCI to use the specified docker image as the runtime environment for you job.
23    # We have selected a pre-built image that mirrors the build environment we use on
24    # the 1.0 platform, but we recommend you choose an image more tailored to the needs
25    # of each job. For more information on choosing an image (or alternatively using a
26    # VM instead of a container) see https://circleci.com/docs/2.0/executor-types/
27    # To see the list of pre-built images that CircleCI provides for most common languages see
28    # https://circleci.com/docs/2.0/circleci-images/
29    docker:
30    - image: circleci/build-image:ubuntu-14.04-XXL-upstart-1189-5614f37
31      command: /sbin/init
32    steps:
33    # Machine Setup
34    #   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
35    # 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.
36    - checkout
37    # Prepare for artifact and test results  collection equivalent to how it was done on 1.0.
38    # In many cases you can simplify this from what is generated here.
39    # 'See docs on artifact collection here https://circleci.com/docs/2.0/artifacts/'
40    - run: mkdir -p $CIRCLE_ARTIFACTS $CIRCLE_TEST_REPORTS
41    # Dependencies
42    #   This would typically go in either a build or a build-and-test job when using workflows
43    # Restore the dependency cache
44    - restore_cache:
45        keys:
46        # This branch if available
47        - v1-dep-{{ .Branch }}-
48        # Default branch if not
49        - v1-dep-dev-
50        # Any branch if there are none on the default branch - this should be unnecessary if you have your default branch configured correctly
51        - v1-dep-
52    # This is based on your 1.0 configuration file or project settings
53    - run: sudo add-apt-repository -y ppa:ubuntu-toolchain-r/test; sudo apt-get -y -qq update
54    - run: sudo apt-get -y install qemu-system-ppc qemu-user-static gcc-powerpc-linux-gnu
55    - run: sudo apt-get -y install qemu-system-arm gcc-arm-linux-gnueabi libc6-dev-armel-cross gcc-aarch64-linux-gnu libc6-dev-arm64-cross
56    - run: sudo apt-get -y install libc6-dev-i386 clang gcc-5 gcc-5-multilib gcc-6 valgrind
57    # Save dependency cache
58    - save_cache:
59        key: v1-dep-{{ .Branch }}-{{ epoch }}
60        paths:
61        # This is a broad list of cache paths to include many possible development environments
62        # You can probably delete some of these entries
63        - vendor/bundle
64        - ~/virtualenvs
65        - ~/.m2
66        - ~/.ivy2
67        - ~/.bundle
68        - ~/.go_workspace
69        - ~/.gradle
70        - ~/.cache/bower
71    # Test
72    #   This would typically be a build job when using workflows, possibly combined with build
73    # This is based on your 1.0 configuration file or project settings
74    - run: clang -v; make clangtest && make clean
75    - run: g++ -v; make gpptest     && make clean
76    - run: gcc -v; make c_standards && make clean
77    - run: gcc -v; g++ -v; make ctocpptest && make clean
78    - run: gcc-5 -v; CC=gcc-5 CFLAGS="-O2 -Werror" make check && make clean
79    - run: gcc-5 -v; CC=gcc-5 CFLAGS="-O2 -m32 -Werror" CPPFLAGS=-I/usr/include/x86_64-linux-gnu make check && make clean
80    - run: gcc-6 -v; CC=gcc-6 make c_standards && make clean
81    - run: gcc-6 -v; CC=gcc-6 MOREFLAGS="-O2 -Werror" make check  && make clean
82    - run: make cmake               && make clean
83    - run: make -C tests test-lz4
84    - run: make -C tests test-lz4c
85    - run: make -C tests test-frametest
86    - run: make -C tests test-fullbench
87    - run: make -C tests test-fuzzer && make clean
88    - run: make -C lib all          && make clean
89    - run: pyenv global 3.4.4; make versionsTest MOREFLAGS=-I/usr/include/x86_64-linux-gnu && make clean
90    - run: make travis-install      && make clean
91    - run: gcc -v; CFLAGS="-O2 -m32 -Werror" CPPFLAGS=-I/usr/include/x86_64-linux-gnu make check && make clean
92    - run: make usan                && make clean
93    - run: clang -v; make staticAnalyze && make clean
94    - run: make -C tests test-mem && make clean
95    - run: make platformTest CC=powerpc-linux-gnu-gcc QEMU_SYS=qemu-ppc-static                  && make clean
96    - run: make platformTest CC=powerpc-linux-gnu-gcc QEMU_SYS=qemu-ppc64-static MOREFLAGS=-m64 && make clean
97    - run: make platformTest CC=arm-linux-gnueabi-gcc QEMU_SYS=qemu-arm-static                  && make clean
98    - run: make platformTest CC=aarch64-linux-gnu-gcc QEMU_SYS=qemu-aarch64-static              && make clean
99    # Teardown
100    #   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
101    # Save test results
102    - store_test_results:
103        path: /tmp/circleci-test-results
104    # Save artifacts
105    - store_artifacts:
106        path: /tmp/circleci-artifacts
107    - store_artifacts:
108        path: /tmp/circleci-test-results
109