This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
discards 3a54271 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards d01863f onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 11d1890 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards d3b2a19 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards fd7855c 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards 5d40424 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards 8227d82 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards 886902e 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards 1bd3374 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 7728945 onsuccess: #380: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]
new 224eae8 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new ea3a4a4 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new 4b8dc7a 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new 5d10d34 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new 14fd046 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new e8659b8 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new a86bfe2 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 6bd4896 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (3a54271)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 9 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
discards 2e589f9 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 4d51b68 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards c2742a7 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards b3f9bf8 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards 8bc5230 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards 4e0ebbc 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards 290493c 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards 681300c 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards ad0ec74 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
discards 29624ad 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new af77c30 onsuccess: #378: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]
new 1bd3374 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 886902e 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new 8227d82 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new 5d40424 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new fd7855c 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new d3b2a19 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new 11d1890 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new d01863f onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 3a54271 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (2e589f9)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 10 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allnoconfig
in repository toolchain/ci/base-artifacts/tcwg_kernel/llvm-master-arm-mainline-allnoconfig.
from 7243b9f onsuccess: #47: all: [TCWG CI] https://ci.linaro.org/job/tcwg [...]
new 6d5e0c7 onsuccess: #48: all: [TCWG CI] https://ci.linaro.org/job/tcwg [...]
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
01-reset_artifacts/console.log.xz | Bin 2312 -> 2308 bytes
02-prepare_abe/console.log.xz | Bin 2600 -> 2652 bytes
03-build_abe-binutils/console.log.xz | Bin 27388 -> 27276 bytes
03-build_abe-binutils/make-binutils.log.xz | Bin 17452 -> 17576 bytes
04-build_kernel_llvm/console.log.xz | Bin 67520 -> 65876 bytes
05-build_abe-qemu/console.log.xz | Bin 34000 -> 34168 bytes
05-build_abe-qemu/make-qemu.log.xz | Bin 22544 -> 22812 bytes
06-build_linux/console.log.xz | Bin 2992 -> 2964 bytes
07-boot_linux/console.log.xz | Bin 496 -> 496 bytes
08-check_regression/console.log.xz | Bin 1244 -> 1192 bytes
git/binutils_rev | 2 +-
git/linux_rev | 2 +-
git/llvm_rev | 2 +-
jenkins/build-name | 2 +-
jenkins/notify-full.log | 283 +++++++++++------------------
jenkins/notify-init.log | 102 +++++------
jenkins/rewrite.log | 16 +-
jenkins/run-build.env | 6 +-
manifest.sh | 4 +-
notify/jira/comment-template.txt | 2 +-
notify/mail-body.txt | 48 +++--
notify/mail-subject.txt | 2 +-
22 files changed, 185 insertions(+), 286 deletions(-)
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
discards 59e0c51 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards cd2e75c onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 9e48c4e 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards 655a6a2 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards ca7bb62 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards 6d5afa4 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards e80a16e 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards 23f5c05 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards c1a3b61 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
discards e64e77b 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
discards 9d9e291 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
new 1b3ff1a force: #377: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk_ [...]
new 29624ad 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new ad0ec74 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 681300c 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new 290493c 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new 4e0ebbc 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new 8bc5230 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new b3f9bf8 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new c2742a7 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new 4d51b68 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 2e589f9 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (59e0c51)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 11 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
discards bed5f2d onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 1c195f7 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards ec845c6 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards ef498f2 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards 781286e 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards 4c0e856 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards 4546096 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards 0297a03 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards 542c54a 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
discards 3ff7934 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
discards 5110970 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
discards 0182ee7 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
new 534edf4 force: #376: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bmk_ [...]
new 9d9e291 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
new e64e77b 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new c1a3b61 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 23f5c05 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new e80a16e 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new 6d5afa4 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new ca7bb62 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new 655a6a2 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new 9e48c4e 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new cd2e75c onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 59e0c51 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (bed5f2d)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 12 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
discards bfd32db onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 736aee2 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards b661608 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards f7dee9c 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards 668c532 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards 6718d15 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards 0809fad 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards 28e4726 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards 48138fe 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
discards 5819e33 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
discards 3b63134 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
discards f59d99c 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
discards 27cfd16 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
new 2efe5ea onsuccess: #375: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]
new 0182ee7 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
new 5110970 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
new 3ff7934 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new 542c54a 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 0297a03 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new 4546096 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new 4c0e856 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new 781286e 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new ef498f2 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new ec845c6 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new 1c195f7 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new bed5f2d onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (bfd32db)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 13 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
discards 6758b20 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 0744bf7 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 168cda3 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards 92b9108 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards c62d5f6 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards 19ac1b5 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards 4bdef7e 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards 003572c 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards fdd253d 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
discards 17222ea 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
discards aa07c34 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
discards b000e93 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
discards b1a167b 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
discards 4c3502c 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
new 65ddeb7 onsuccess: #374: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]
new 27cfd16 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
new f59d99c 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
new 3b63134 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
new 5819e33 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new 48138fe 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 28e4726 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new 0809fad 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new 6718d15 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new 668c532 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new f7dee9c 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new b661608 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new 736aee2 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new bfd32db onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (6758b20)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 14 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.
This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_speed-spec2k6/gnu-aarch64-master-O3_LTO.
discards 78700bb onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 4463e00 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards d072500 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
discards d238d20 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
discards 86a6de3 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
discards c5d1f8b 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
discards 1fd30dd 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
discards d497344 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
discards 2e715fd 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
discards 3ca1daf 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
discards 90d893f 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
discards 06053b7 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
discards b5166c2 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
discards e69f13f 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
discards c7f425f 9: onsuccess: #370: 1: [TCWG CI] No change after binutils/gcc [...]
new 4c5fea1 onsuccess: #370: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_ [...]
new 4c3502c 10: onsuccess: #374: 1: [TCWG CI] No change after binutils: 3 [...]
new b1a167b 11: onsuccess: #375: 1: [TCWG CI] 456.hmmer speeds up by -4% [...]
new b000e93 12: force: #376: 1: [TCWG CI] 456.hmmer slowed down by 4% aft [...]
new aa07c34 13: force: #377: 1: [TCWG CI] 403.gcc failed to build after b [...]
new 17222ea 14: onsuccess: #378: 1: [TCWG CI] No change after gcc: 20 commits
new fdd253d 15: onsuccess: #380: 1: [TCWG CI] No change after binutils: 1 [...]
new 003572c 16: onsuccess: #382: 1: [TCWG CI] 403.gcc built and run OK af [...]
new 4bdef7e 17: onsuccess: #384: 1: [TCWG CI] No change after binutils: 6 [...]
new 19ac1b5 18: onsuccess: #385: 1: [TCWG CI] No change after gcc: 78 commits
new c62d5f6 19: onsuccess: #386: 1: [TCWG CI] No change after glibc: 17 commits
new 92b9108 20: onsuccess: #387: 1: [TCWG CI] No change after v5.19.11-39 [...]
new 168cda3 21: onsuccess: #388: 1: [TCWG CI] No change after binutils/gc [...]
new 0744bf7 onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 6758b20 onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (78700bb)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_speed-spec2k6/g [...]
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omits" are not gone; other references still
refer to them. Any revisions marked "discards" are gone forever.
The 15 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "adds" were already present in the repository and have only
been added to this reference.
Summary of changes:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.