-
Notifications
You must be signed in to change notification settings - Fork 4
/
.travis.yml
47 lines (41 loc) · 3.3 KB
/
.travis.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
language: verilog
services:
- docker
before_install:
- docker build -t icarus-verilog_rv32i .
jobs:
include:
- stage: Unit Tests # naming the Tests stage
name: "Arithmeticologic Tests" # names the first Tests stage job
script: docker run icarus-verilog_rv32i /bin/sh -c "iverilog -grelative-include -o bin/al tb/arithmeticologic.v ; bin/al| tee /dev/fd/2 | grep -q 'FATAL' && exit 1 || exit 0;"
- stage: Unit Tests # naming the Tests stage
name: "Load-Store Tests" # names the second Tests stage job
script: docker run icarus-verilog_rv32i /bin/sh -c "iverilog -grelative-include -o bin/ls tb/load_store.v ; bin/ls| tee /dev/fd/2 | grep -q 'FATAL' && exit 1 || exit 0;"
- stage: Unit Tests # naming the Tests stage
name: "Branch Tests" # names the second Tests stage job
script: docker run icarus-verilog_rv32i /bin/sh -c "iverilog -grelative-include -o bin/br tb/branch.v ; bin/br| tee /dev/fd/2 | grep -q 'FATAL' && exit 1 || exit 0;"
- stage: Unit Tests # naming the Tests stage
name: "CSR Tests" # names the second Tests stage job
script: docker run icarus-verilog_rv32i /bin/sh -c "iverilog -grelative-include -o bin/br tb/csr.v ; bin/br| tee /dev/fd/2 | grep -q 'FATAL' && exit 1 || exit 0;"
- stage: Unit Tests # naming the Tests stage
name: "Arithmeticologic Tests RAM_MUX" # names the first Tests stage job
script: docker run icarus-verilog_rv32i /bin/sh -c "iverilog -grelative-include -DRAM_MUX_CORE -o bin/al tb/arithmeticologic.v ; bin/al| tee /dev/fd/2 | grep -q 'FATAL' && exit 1 || exit 0;"
- stage: Unit Tests # naming the Tests stage
name: "Load-Store Tests RAM_MUX" # names the second Tests stage job
script: docker run icarus-verilog_rv32i /bin/sh -c "iverilog -grelative-include -DRAM_MUX_CORE -o bin/ls tb/load_store.v ; bin/ls| tee /dev/fd/2 | grep -q 'FATAL' && exit 1 || exit 0;"
- stage: Unit Tests # naming the Tests stage
name: "Branch Tests RAM_MUX" # names the second Tests stage job
script: docker run icarus-verilog_rv32i /bin/sh -c "iverilog -grelative-include -DRAM_MUX_CORE -o bin/br tb/branch.v ; bin/br| tee /dev/fd/2 | grep -q 'FATAL' && exit 1 || exit 0;"
- stage: Unit Tests # naming the Tests stage
name: "CSR Tests RAM_MUX" # names the second Tests stage job
script: docker run icarus-verilog_rv32i /bin/sh -c "iverilog -grelative-include -DRAM_MUX_CORE -o bin/br tb/csr.v ; bin/br| tee /dev/fd/2 | grep -q 'FATAL' && exit 1 || exit 0;"
# - stage: Unit Tests # naming the Tests stage
# name: "Error example" # names the second Tests stage job
# script: docker run icarus-verilog_rv32i /bin/sh -c "iverilog -grelative-include -DCUSTOM_DEFINE -DRAM_MUX_CORE -o bin/er tb/error_test.v ; bin/er | tee /dev/fd/2 | grep -q 'FATAL' && exit 1 || exit 0;"
- stage: build docker image
script:
- echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin
- docker build -t icarus-verilog_rv32i .
- docker images
- docker tag icarus-verilog_rv32i $DOCKER_USERNAME/icarus-verilog_rv32i
- docker push $DOCKER_USERNAME/icarus-verilog_rv32i