forked from NOAA-OWP/ngen
-
Notifications
You must be signed in to change notification settings - Fork 0
406 lines (343 loc) · 12.4 KB
/
test_and_validate.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
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
# Test changes that have been pushed to the master and dev branches
name: Testing and Validation
# Controls when the action will run.
on:
push:
branches: [ master, dev, notreal ]
pull_request:
branches: [ master, dev, notreal ]
workflow_dispatch:
env:
# Obtained from https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources
# TODO: add something later that can check the runners for hyperthreading
LINUX_NUM_PROC_CORES: 2
MACOS_NUM_PROC_CORES: 3
ASAN_OPTIONS: detect_leaks=false
# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
# Run general unit tests in linux environment
test_unit:
# The type of runner that the job will run on
strategy:
matrix:
os: [ubuntu-latest, macos-latest]
fail-fast: false
runs-on: ${{ matrix.os }}
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
- name: Checkout the commit
uses: actions/checkout@v2
- name: Build Unit Tests
uses: ./.github/actions/ngen-build
with:
targets: "test_unit test_geopackage"
build-cores: ${{ env.LINUX_NUM_PROC_CORES }}
- name: Run Tests
run: ./cmake_build/test/test_unit
timeout-minutes: 15
- name: Run GeoPackage Tests
run: |
# Container underflow report is a false positive, from a build with instrumentation
# disabled in one file where it hangs the compiler (ngen#567)
export ASAN_OPTIONS=${ASAN_OPTIONS}:detect_container_overflow=0
./cmake_build/test/test_geopackage
timeout-minutes: 15
- name: Clean Up
uses: ./.github/actions/clean-build
# Test PET
test_pet:
# The type of runner that the job will run on
strategy:
matrix:
os: [ubuntu-latest, macos-latest]
fail-fast: false
runs-on: ${{ matrix.os }}
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
- name: Build PET Submodule
id: submod_build_5
uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/evapotranspiration/evapotranspiration"
targets: "petbmi"
- name: Build PET Tests
uses: ./.github/actions/ngen-build
with:
targets: "compare_pet"
build-cores: ${{ env.LINUX_NUM_PROC_CORES }}
- name: Run Tests
run: ./cmake_build/test/compare_pet
timeout-minutes: 15
- name: Clean Up
uses: ./.github/actions/clean-build
# Test MPI remote nexus behavior in linux
test_mpi_remote_nexus:
# The type of runner that the job will run on
strategy:
matrix:
os: [ubuntu-latest]
fail-fast: false
runs-on: ${{ matrix.os }}
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
- name: Build Unit Tests
uses: ./.github/actions/ngen-build
with:
targets: "test_remote_nexus"
build-cores: ${{ env.LINUX_NUM_PROC_CORES }}
use_mpi: 'ON'
- name: run_tests
run: mpirun --allow-run-as-root -np 2 ./cmake_build/test/test_remote_nexus
timeout-minutes: 15
- name: Clean Up
uses: ./.github/actions/clean-build
# Run BMI C++ tests in linux environment
test_bmi_cpp:
# The type of runner that the job will run on
strategy:
matrix:
os: [ubuntu-latest, macos-latest]
fail-fast: false
runs-on: ${{ matrix.os }}
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
#make sure cxx bmi is initialized/ready
- uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/bmi-cxx/"
- name: Build Submodules
id: submod_build
uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/test_bmi_cpp/"
targets: "testbmicppmodel"
- name: Build Unit Tests
uses: ./.github/actions/ngen-build
with:
targets: "test_bmi_cpp"
build-cores: ${{ env.LINUX_NUM_PROC_CORES }}
- name: Run Tests
run: |
cd ./cmake_build/test/
./test_bmi_cpp
cd ../../
timeout-minutes: 15
- name: Clean Up Unit Test Build
uses: ./.github/actions/clean-build
- name: Clean Up Submodule Build
uses: ./.github/actions/clean-build
with:
build-dir: ${{ steps.submod_build.outputs.build-dir }}
# Run BMI C tests in linux environment, and separating to isolate
test_bmi_c:
# The type of runner that the job will run on
strategy:
matrix:
os: [ubuntu-latest, macos-latest]
fail-fast: false
runs-on: ${{ matrix.os }}
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
- name: Build Submodules
id: submod_build
uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/test_bmi_c"
targets: "testbmicmodel"
- name: Build Unit Tests
uses: ./.github/actions/ngen-build
with:
targets: "test_bmi_c"
build-cores: ${{ env.LINUX_NUM_PROC_CORES }}
bmi_c: 'ON'
#Is this required for this test???
use_python: 'ON'
- name: run_bmi_c_tests
run: |
cd ./cmake_build/test/
./test_bmi_c
cd ../../
timeout-minutes: 15
- name: Clean Up Unit Test Build
uses: ./.github/actions/clean-build
- name: Clean Up Submodule Build
uses: ./.github/actions/clean-build
with:
build-dir: ${{ steps.submod_build.outputs.build-dir }}
# As with the BMI C ubuntu job, separate Fortran in linux tests to keep setups clean and cause of failures clear.
test_bmi_fortran:
# The type of runner that the job will run on
strategy:
matrix:
os: [ubuntu-latest, macos-latest]
fail-fast: false
runs-on: ${{ matrix.os }}
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
- name: Build Submodules
id: submod_build_1
uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/test_bmi_fortran/"
- name: Build Submodules
id: submod_build_2
uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/iso_c_fortran_bmi/"
- name: Build Unit Tests
uses: ./.github/actions/ngen-build
with:
targets: "test_bmi_fortran"
build-cores: ${{ env.LINUX_NUM_PROC_CORES }}
#is this required for this test?
bmi_c: 'ON'
bmi_fortran: 'ON'
- name: Run Unit Tests
run: |
cd ./cmake_build/test/
./test_bmi_fortran
cd ../../
timeout-minutes: 15
- name: Clean Up Unit Test Build
uses: ./.github/actions/clean-build
- name: Clean Up Submodule Build
uses: ./.github/actions/clean-build
with:
build-dir: ${{ steps.submod_build_1.outputs.build-dir }}
- uses: ./.github/actions/clean-build
with:
build-dir: ${{ steps.submod_build_2.outputs.build-dir }}
# As with the BMI C ubuntu job, separate Python in linux tests to keep setups clean and cause of failures clear.
test_bmi_python:
# The type of runner that the job will run on
strategy:
matrix:
os: [ubuntu-latest, macos-latest]
fail-fast: false
runs-on: ${{ matrix.os }}
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out repository under $GITHUB_WORKSPACE, so job can access it
- uses: actions/checkout@v2
- name: Build Unit Tests
uses: ./.github/actions/ngen-build
with:
targets: "test_bmi_python"
build-cores: ${{ env.LINUX_NUM_PROC_CORES }}
#is this required for this test?
bmi_c: 'ON'
use_python: 'ON'
additional_python_requirements: 'extern/test_bmi_py/requirements.txt'
- name: run_bmi_python_tests
run: |
cd ./cmake_build/test/
./test_bmi_python
cd ../../
timeout-minutes: 15
- name: Clean Up Unit Test Build
uses: ./.github/actions/clean-build
# As with the BMI C ubuntu job, separate multi BMI in linux tests to keep setups clean and cause of failures clear.
test_bmi_multi:
# The type of runner that the job will run on
strategy:
matrix:
os: [ubuntu-latest, macos-latest]
fail-fast: false
runs-on: ${{ matrix.os }}
# Steps represent a sequence of tasks that will be executed as part of the job
steps:
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
- uses: actions/checkout@v2
- name: Build Submodules
id: submod_build_1
uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/test_bmi_fortran/"
- name: Build Submodules
id: submod_build_2
uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/iso_c_fortran_bmi/"
- name: Build Submodules
id: submod_build_3
uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/test_bmi_c/"
targets: "testbmicmodel"
#make sure cxx bmi is initialized/ready
- uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/bmi-cxx/"
- name: Build Submodules
id: submod_build_4
uses: ./.github/actions/ngen-submod-build
with:
mod-dir: "extern/test_bmi_cpp/"
targets: "testbmicppmodel"
- name: Build Unit Tests
uses: ./.github/actions/ngen-build
with:
targets: "test_bmi_multi"
build-cores: ${{ env.LINUX_NUM_PROC_CORES }}
bmi_c: 'ON'
bmi_fortran: 'ON'
use_python: 'ON'
additional_python_requirements: 'extern/test_bmi_py/requirements.txt'
- name: Run Unit Tests
run: ./cmake_build/test/test_bmi_multi
timeout-minutes: 15
- name: Clean Up Unit Test Build
uses: ./.github/actions/clean-build
- name: Clean Up Submodule Build
uses: ./.github/actions/clean-build
with:
build-dir: ${{ steps.submod_build_1.outputs.build-dir }}
- uses: ./.github/actions/clean-build
with:
build-dir: ${{ steps.submod_build_2.outputs.build-dir }}
- uses: ./.github/actions/clean-build
with:
build-dir: ${{ steps.submod_build_3.outputs.build-dir }}
- uses: ./.github/actions/clean-build
with:
build-dir: ${{ steps.submod_build_4.outputs.build-dir }}
# TODO: fails due to compilation error, at least in large part due to use of POSIX functions not supported on Windows.
# TODO: Need to determine whether Windows support (in particular, development environment support) is necessary.
# test_unit_windows_latest:
# # The type of runner that the job will run on
# runs-on: windows-latest
#
# # Steps represent a sequence of tasks that will be executed as part of the job
# steps:
# # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
# - uses: actions/checkout@v2
#
# - name: git submodule
# run: git submodule update --init --recursive -- test/googletest
#
# - name: cmake_init_build
# run: cmake -B cmake_build -S .
#
# - name: build_tests
# run: cmake --build cmake_build --target test_unit
# timeout-minutes: 15
#
# - name: run_tests
# run: ./cmake_build/test/test_unit
# timeout-minutes: 15
#
# - name: clean_build
# run: cmake --build cmake_build --target clean
#
# - name: cleanup_dir
# run: rm -rf cmake_build