11-check_regression/baseline.xfail | 0
11-check_regression/console.log.xz | Bin 0 -> 2640 bytes
11-check_regression/fails.sum | 6 +++++
11-check_regression/flaky.xfail | 2 ++
README.html | 32 +++------------------------
README.txt | 31 ++------------------------
sumfiles/xfails.xfail | 44 ++-----------------------------------
7 files changed, 15 insertions(+), 100 deletions(-)
diff --git a/11-check_regression/baseline.xfail b/11-check_regression/baseline.xfail
new file mode 100644
index 00000000..e69de29b
diff --git a/11-check_regression/console.log.xz b/11-check_regression/console.log.xz
new file mode 100644
index 00000000..86495b12
Binary files /dev/null and b/11-check_regression/console.log.xz differ
diff --git a/11-check_regression/fails.sum b/11-check_regression/fails.sum
new file mode 100644
index 00000000..a241db49
--- /dev/null
+++ b/11-check_regression/fails.sum
@@ -0,0 +1,6 @@
+
+ === Results Summary ===
+
+# of stable fails 0
+# of flaky entries 0
+# of all tests 325
diff --git a/11-check_regression/flaky.xfail b/11-check_regression/flaky.xfail
new file mode 100644
index 00000000..a1a0a1ba
--- /dev/null
+++ b/11-check_regression/flaky.xfail
@@ -0,0 +1,2 @@
+################################
+# Known flaky tests
diff --git a/README.html b/README.html
index a026f637..fd6e2843 100644
--- a/README.html
+++ b/README.html
@@ -11,14 +11,6 @@ the build. More synthetic information is available in other directories,
as described below:
-- 00-sumfiles/ 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.
-
- git/ contains the revision and repository of each toolchain
component built
@@ -40,32 +32,11 @@ interested in:
List of files below:
-- ./00-sumfiles/gdb.log.xz
-
- ./01-reset_artifacts/console.log.xz
-
- ./02-prepare_abe/console.log.xz
-
- ./03-build_abe-binutils/console.log.xz
-
- ./03-build_abe-binutils/make-binutils.log.xz
-
- ./04-build_abe-gcc/console.log.xz
-
- ./04-build_abe-gcc/make-gcc-stage2.log.xz
-
- ./05-clean_sysroot/console.log.xz
-
- ./06-build_abe-linux/console.log.xz
-
- ./07-build_abe-glibc/console.log.xz
-
- ./07-build_abe-glibc/make-glibc.log.xz
-
- ./08-build_abe-gdb/console.log.xz
-
- ./08-build_abe-gdb/make-gdb.log.xz
-
- ./09-build_abe-dejagnu/console.log.xz
-
- ./09-build_abe-dejagnu/make-dejagnu.log.xz
-
- ./10-build_abe-check_gdb/baseline.xfail
-
- ./10-build_abe-check_gdb/check-gdb.log.xz
-
- ./10-build_abe-check_gdb/console.log.xz
-
- ./10-build_abe-check_gdb/flaky.xfail
- ./11-check_regression/baseline.xfail
- ./11-check_regression/console.log.xz
- ./11-check_regression/fails.sum
@@ -84,11 +55,13 @@ List of files below:
- ./jenkins/notify-full.log
- ./jenkins/notify-init.log
- ./jenkins/rewrite-false.log
+
- ./jenkins/rewrite-true.log
- ./jenkins/run-build.env
- ./manifest.sh
- ./notify/configure-toolchain.txt
- ./notify/fixes.sum
- ./notify/jira/comment-template.txt
+
- ./notify/lnt_report.json
- ./notify/mail-body.txt
- ./notify/mail-recipients.txt
- ./notify/mail-subject.txt
@@ -96,6 +69,7 @@ List of files below:
- ./notify/results.compare.txt
- ./notify/results-summary.txt
- ./README.html
+
- ./README.txt
- ./results
- ./rr_stage.txt
- ./sumfiles/gdb.sum
diff --git a/README.txt b/README.txt
index 823b2c0b..3eed524e 100644
--- a/README.txt
+++ b/README.txt
@@ -8,14 +8,6 @@ the build. More synthetic information is available in other directories,
as described below:
-- 00-sumfiles/ 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.
-
- git/ contains the revision and repository of each toolchain
component built
@@ -37,32 +29,11 @@ interested in:
- notify/regressions.sum and notify/results.compare.txt (regression report).
-- 00-sumfiles/ .log files with detailed errors, to save
- yourself reproducing the problem on your machine.
List of files below:
-- ./00-sumfiles/gdb.log.xz
-- ./01-reset_artifacts/console.log.xz
-- ./02-prepare_abe/console.log.xz
-- ./03-build_abe-binutils/console.log.xz
-- ./03-build_abe-binutils/make-binutils.log.xz
-- ./04-build_abe-gcc/console.log.xz
-- ./04-build_abe-gcc/make-gcc-stage2.log.xz
-- ./05-clean_sysroot/console.log.xz
-- ./06-build_abe-linux/console.log.xz
-- ./07-build_abe-glibc/console.log.xz
-- ./07-build_abe-glibc/make-glibc.log.xz
-- ./08-build_abe-gdb/console.log.xz
-- ./08-build_abe-gdb/make-gdb.log.xz
-- ./09-build_abe-dejagnu/console.log.xz
-- ./09-build_abe-dejagnu/make-dejagnu.log.xz
-- ./10-build_abe-check_gdb/baseline.xfail
-- ./10-build_abe-check_gdb/check-gdb.log.xz
-- ./10-build_abe-check_gdb/console.log.xz
-- ./10-build_abe-check_gdb/flaky.xfail
- ./11-check_regression/baseline.xfail
- ./11-check_regression/console.log.xz
- ./11-check_regression/fails.sum
@@ -81,11 +52,13 @@ List of files below:
- ./jenkins/notify-full.log
- ./jenkins/notify-init.log
- ./jenkins/rewrite-false.log
+- ./jenkins/rewrite-true.log
- ./jenkins/run-build.env
- ./manifest.sh
- ./notify/configure-toolchain.txt
- ./notify/fixes.sum
- ./notify/jira/comment-template.txt
+- ./notify/lnt_report.json
- ./notify/mail-body.txt
- ./notify/mail-recipients.txt
- ./notify/mail-subject.txt
diff --git a/sumfiles/xfails.xfail b/sumfiles/xfails.xfail
index 9434b4b6..a91770d0 100644
--- a/sumfiles/xfails.xfail
+++ b/sumfiles/xfails.xfail
@@ -3,47 +3,7 @@
# - known flaky tests (from baseline)
# - known failures (from baseline)
#
+################################
# Known flaky tests
-
-# From https://ci.linaro.org/job/tcwg_gnu_native_fast_check_gdb--master-arm-build/868/:
- === gdb tests ===
-
-Running gdb:gdb.base/breakpoint-in-ro-region.exp ...
-flaky,expire=20241210 | FAIL: gdb.base/breakpoint-in-ro-region.exp: get lo address of main
-
- === Results Summary ===
-
-# of stable fails 3
-# of flaky entries 0
-# of all tests 4
- === gdb tests ===
-
-Running gdb:gdb.base/breakpoint-in-ro-region.exp ...
-flaky,expire=20241210 | FAIL: gdb.base/breakpoint-in-ro-region.exp: get lo address of main (timeout)
-
- === Results Summary ===
-
-# of stable fails 3
-# of flaky entries 0
-# of all tests 4
- === gdb tests ===
-
-Running gdb:gdb.base/breakpoint-in-ro-region.exp ...
-flaky,expire=20241210 | FAIL: gdb.base/breakpoint-in-ro-region.exp: set debug target 0 (timeout)
-
- === Results Summary ===
-
-# of stable fails 2
-# of flaky entries 2
-# of all tests 4
- === gdb tests ===
-
-Running gdb:gdb.base/breakpoint-in-ro-region.exp ...
-flaky,expire=20241210 | FAIL: gdb.base/breakpoint-in-ro-region.exp: probe target hardware step (timeout)
-
- === Results Summary ===
-
-# of stable fails 1
-# of flaky entries 3
-# of all tests 40
+################################
# Known failures (from baseline)