-
Notifications
You must be signed in to change notification settings - Fork 517
Expand file tree
/
Copy pathcodecov.yml
More file actions
103 lines (98 loc) · 3.53 KB
/
Copy pathcodecov.yml
File metadata and controls
103 lines (98 loc) · 3.53 KB
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
# Configuration for https://codecov.io. After changing it, validate it with
# curl -X POST --data-binary @codecov.yml https://codecov.io/validate
# See https://docs.codecov.com/docs/codecovyml-reference for the full reference.
codecov:
notify:
# Comment as soon as a report has been processed instead of holding the
# comment back until every other CI status has completed. A pull request
# whose build or tests fail is one where the report is wanted most, and
# the comment is updated in place as the remaining uploads arrive.
wait_for_ci: false
comment:
layout: "header, reach, diff, components, files, footer"
behavior: default
# Comment on every pull request: also on one that changes no coverage at
# all ...
require_changes: false
# ... on one whose base commit has no report to compare against ...
require_base: false
# ... and on one for which no coverage was uploaded, so that the test
# results are reported even when the coverage build did not get that far.
require_head: false
parsers:
gcov:
branch_detection:
conditional: yes
loop: yes
method: no
macro: no
flags:
# The four components are uploaded separately, each from the build
# directory that holds its gcov reports; see the coverage job of
# .github/workflows/special.yml. Their coverage is therefore already
# separated at upload time and needs no path filtering here.
blas:
carryforward: true
cblas:
carryforward: true
lapack:
carryforward: true
lapacke:
carryforward: true
# The same four groups once more, as components. A flag is attached to an
# upload and so depends on the coverage job splitting its uploads the way it
# does; a component is a filter over whatever coverage arrives, so these keep
# reporting the four libraries separately even if that split ever changes.
# The paths are the source directories the libraries are built from, which is
# also how the CMake build directories the uploads use are laid out.
component_management:
individual_components:
- component_id: blas
name: BLAS
paths:
- BLAS/SRC/**
- component_id: cblas
name: CBLAS
paths:
- CBLAS/src/**
- CBLAS/include/**
- component_id: lapack
name: LAPACK
paths:
# The LAPACK library is built from SRC together with the machine
# parameter and support routines it takes from INSTALL; see the
# ../INSTALL/ entries in SRC/CMakeLists.txt.
- SRC/**
- INSTALL/**
- component_id: lapacke
name: LAPACKE
paths:
- LAPACKE/src/**
- LAPACKE/utils/**
- component_id: tmglib
name: TMGLIB
paths:
# The test matrix generators. Shipped as a library of their own and
# used by every LAPACK test to build its inputs, so a generator path
# no test asks for shows up here rather than in any of the above.
- TESTING/MATGEN/**
# The test programs, one component per library they exercise. These
# measure the tests themselves, not the code under test: a routine here
# that never runs is a test that was written and then never reached.
- component_id: blas_testing
name: BLAS testing
paths:
- BLAS/TESTING/**
- component_id: cblas_testing
name: CBLAS testing
paths:
- CBLAS/testing/**
- component_id: lapack_testing
name: LAPACK testing
paths:
- TESTING/LIN/**
- TESTING/EIG/**
- component_id: lapacke_testing
name: LAPACKE testing
paths:
- LAPACKE/testing/**