-
Notifications
You must be signed in to change notification settings - Fork 74
52 lines (50 loc) · 1.93 KB
/
multi-device-build-and-unit-tests.yaml
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
48
49
50
51
52
name: "Multi-chip unit tests"
on:
workflow_dispatch:
schedule:
- cron: "0 */3 * * *" # This cron schedule runs the workflow every 3 hours
jobs:
multi-chip-unit-tests:
strategy:
# Do not fail-fast because we need to ensure all tests go to completion
# so we try not to get hanging machines
fail-fast: false
matrix:
test-group: [
# N300 2x4
{
name: "T3000 unit tests",
arch: wormhole_b0,
runs-on: ["wormhole_b0", "multi-chip-num-pcie-4", "multi-chip-num-chips-8"],
cmd: './tests/scripts/run_tests.sh --tt-arch wormhole_b0 --pipeline-type post_commit_multi_device --dispatch-mode ""'
},
# {
# name: "T3000 unstable tests",
# arch: wormhole_b0,
# runs-on: ["wormhole_b0", "multi-chip-num-pcie-4", "multi-chip-num-chips-8"],
# cmd: './tests/scripts/run_tests.sh --tt-arch wormhole_b0 --pipeline-type post_commit_multi_device_unstable --dispatch-mode ""'
# },
]
name: ${{ matrix.test-group.name }} ${{ matrix.test-group.arch }}
env:
TT_METAL_ENV: ${{ vars.TT_METAL_ENV }}
ARCH_NAME: ${{ matrix.test-group.arch }}
CONFIG: ci
environment: dev
runs-on: ${{ matrix.test-group.runs-on }}
steps:
- uses: tenstorrent-metal/metal-workflows/.github/actions/[email protected]
- name: Set up dyanmic env vars for build
run: |
echo "TT_METAL_HOME=$(pwd)" >> $GITHUB_ENV
- name: Build tt-metal and libs
run: |
PYTHON_ENV_DIR=$(pwd)/build/python_env ./build_metal.sh
- name: Build tt-metal CPP tests
run: cmake --build build --target tests -- -j`nproc`
- name: Run pre/post regression tests
timeout-minutes: 100
run: |
source build/python_env/bin/activate
export PYTHONPATH=$TT_METAL_HOME
${{ matrix.test-group.cmd }}