blob: 3a7b2231552ba51b51e71f7947b81df71665e87c (
plain)
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
|
<!DOCTYPE html>
<html>
<body>
<font color="black">
<h2>How to browse artifacts of this build</h2>
The artifact directories contain a lot of information related to the
results of this build.
<p>
Directories starting with a number contain the logs of each step of
the build. More synthetic information is available in other directories,
as described below:
<p>
<ul>
<li><a href="00-sumfiles/">00-sumfiles/</a> (if present) contains .log and possibly .sum files
generated by the build. Files with .0 suffix contain the results of
the initial full testsuite run, files with .1, .2 etc... contain
logs restricted to the parts (.exp) of the testsuite where we
detected regressions. .1, .2, .... represent the number of times
this subset of the testsuite was executed in order to also identify
flaky tests. The last one contains what is considered as the
results of this build.
<li><a href="git/">git/</a> contains the revision and repository of each toolchain
component built
<li><a href="jenkins/">jenkins/</a> contains information useful for the CI maintainers
<li><a href="notify/">notify/</a> contains the material used to build various
notifications/reports (emails, Jira, LNT, ...)
<li><a href="sumfiles/">sumfiles/</a> contains the .sum files produced by this build.
</ul>
<p>
If you received a notification about one of your patches causing
problems, the information you received is in <a href="notify/">notify/</a> and has
links to other artifacts from this directory.
<p>
If you are investigating such a problem, you are probably primarily
interested in:
<p>
<ul>
<li><a href="notify/results.compare.txt">notify/results.compare.txt</a> (regression report).
<li><a href="00-sumfiles/">00-sumfiles/</a> .log files with detailed errors, to save
yourself reproducing the problem on your machine.
</ul>
</body>
</html>
|
