 04-check_regression/console.log.xz      | Bin 0 -> 2556 bytes
 04-check_regression/results.regressions |   1 +
 04-check_regression/trigger-bisect      |   2 ++
 README.html                             |  14 ++------------
 README.txt                              |  13 +------------
 results                                 |   1 +
 6 files changed, 7 insertions(+), 24 deletions(-)

diff --git a/04-check_regression/console.log.xz b/04-check_regression/console.log.xz
new file mode 100644
index 0000000..1a5452e
Binary files /dev/null and b/04-check_regression/console.log.xz differ
diff --git a/04-check_regression/results.regressions b/04-check_regression/results.regressions
new file mode 100644
index 0000000..b54a4cd
--- /dev/null
+++ b/04-check_regression/results.regressions
@@ -0,0 +1 @@
+# First few build errors in logs:
diff --git a/04-check_regression/trigger-bisect b/04-check_regression/trigger-bisect
new file mode 100644
index 0000000..e88acb5
--- /dev/null
+++ b/04-check_regression/trigger-bisect
@@ -0,0 +1,2 @@
+current_project=llvm
+bad_git=https://github.com/llvm/llvm-project.git#23e3cbb2e82b62586266116c8ab77ce68e412cf8
diff --git a/README.html b/README.html
index 92c2a6f..5c77508 100644
--- a/README.html
+++ b/README.html
@@ -11,14 +11,6 @@ the build.  More synthetic information is available in other directories,
 as described below:
 <p>
 <ul>
-<li><a href="00-sumfiles/">00-sumfiles/</a> 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
 
@@ -35,10 +27,6 @@ links to other artifacts from this directory.
 List of files below:
 <p>
 <ul>
-<li><a href="./01-reset_artifacts/console.log.xz">./01-reset_artifacts/console.log.xz</a>
-<li><a href="./02-build_llvm/configure-toolchain.sh/*view*/">./02-build_llvm/configure-toolchain.sh</a>
-<li><a href="./02-build_llvm/console.log.xz">./02-build_llvm/console.log.xz</a>
-<li><a href="./03-test_llvm/console.log.xz">./03-test_llvm/console.log.xz</a>
 <li><a href="./04-check_regression/console.log.xz">./04-check_regression/console.log.xz</a>
 <li><a href="./04-check_regression/results.regressions/*view*/">./04-check_regression/results.regressions</a>
 <li><a href="./04-check_regression/trigger-bisect/*view*/">./04-check_regression/trigger-bisect</a>
@@ -52,6 +40,7 @@ List of files below:
 <li><a href="./jenkins/notify-full.log/*view*/">./jenkins/notify-full.log</a>
 <li><a href="./jenkins/notify-init.log/*view*/">./jenkins/notify-init.log</a>
 <li><a href="./jenkins/rewrite-false.log/*view*/">./jenkins/rewrite-false.log</a>
+<li><a href="./jenkins/rewrite-true.log/*view*/">./jenkins/rewrite-true.log</a>
 <li><a href="./jenkins/run-build.env/*view*/">./jenkins/run-build.env</a>
 <li><a href="./manifest.sh/*view*/">./manifest.sh</a>
 <li><a href="./notify/configure-toolchain.txt/*view*/">./notify/configure-toolchain.txt</a>
@@ -60,6 +49,7 @@ List of files below:
 <li><a href="./notify/mail-recipients.txt/*view*/">./notify/mail-recipients.txt</a>
 <li><a href="./notify/mail-subject.txt/*view*/">./notify/mail-subject.txt</a>
 <li><a href="./README.html/*view*/">./README.html</a>
+<li><a href="./README.txt/*view*/">./README.txt</a>
 <li><a href="./results/*view*/">./results</a>
 <li><a href="./rr_stage.txt/*view*/">./rr_stage.txt</a>
 </ul>
diff --git a/README.txt b/README.txt
index d7faa28..a46dad4 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
 
@@ -32,10 +24,6 @@ links to other artifacts from this directory.
 List of files below:
 
 
-- ./01-reset_artifacts/console.log.xz
-- ./02-build_llvm/configure-toolchain.sh
-- ./02-build_llvm/console.log.xz
-- ./03-test_llvm/console.log.xz
 - ./04-check_regression/console.log.xz
 - ./04-check_regression/results.regressions
 - ./04-check_regression/trigger-bisect
@@ -49,6 +37,7 @@ 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
diff --git a/results b/results
index 570fa7d..1fe2b3f 100644
--- a/results
+++ b/results
@@ -5,3 +5,4 @@
 # test_llvm:
 # FAILED
 # First few build errors in logs:
+# First few build errors in logs:
