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_size-cpu2017rate/gnu-arm-master-Os_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_size-cpu2017rate/gnu-arm-master-Os_LTO.
discards 54fae06 onsuccess: #97: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards e2c5bad onsuccess: #96: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 93c35f4 onsuccess: #95: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new b28a115 onsuccess: #95: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new af5e648 onsuccess: #96: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new cc886e5 onsuccess: #97: 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 (54fae06)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_size-cpu2017rat [...]
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 3 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_size-cpu2017rate/gnu-arm-master-Os_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_size-cpu2017rate/gnu-arm-master-Os_LTO.
discards 5ba86fb onsuccess: #97: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards a2e7d78 onsuccess: #96: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 8ff3169 onsuccess: #95: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 44c4c88 onsuccess: #94: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 16183f8 onsuccess: #94: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 93c35f4 onsuccess: #95: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new e2c5bad onsuccess: #96: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 54fae06 onsuccess: #97: 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 (5ba86fb)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_size-cpu2017rat [...]
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 4 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_size-cpu2017rate/gnu-arm-master-Os_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_size-cpu2017rate/gnu-arm-master-Os_LTO.
discards 6d72f2a onsuccess: #97: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards d2d8e9f onsuccess: #96: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards c0d6997 onsuccess: #95: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 69ed938 onsuccess: #94: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 565ac20 onsuccess: #93: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new d632ed3 onsuccess: #93: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 44c4c88 onsuccess: #94: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 8ff3169 onsuccess: #95: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new a2e7d78 onsuccess: #96: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 5ba86fb onsuccess: #97: 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 (6d72f2a)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_size-cpu2017rat [...]
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 5 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_size-cpu2017rate/gnu-arm-master-Os_LTO
in repository toolchain/ci/base-artifacts/tcwg_bmk-code_size-cpu2017rate/gnu-arm-master-Os_LTO.
discards 2af7212 onsuccess: #97: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 7502188 onsuccess: #96: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 7608b9d onsuccess: #95: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 94777f4 onsuccess: #94: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards f8835e3 onsuccess: #93: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
discards 777907b onsuccess: #92: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new f2e8d3b onsuccess: #92: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 565ac20 onsuccess: #93: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 69ed938 onsuccess: #94: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new c0d6997 onsuccess: #95: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new d2d8e9f onsuccess: #96: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_b [...]
new 6d72f2a onsuccess: #97: 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 (2af7212)
\
N -- N -- N refs/heads/linaro-local/ci/tcwg_bmk-code_size-cpu2017rat [...]
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 6 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.