This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/08/38708/2
in repository toolchain/jenkins-scripts.
discards 99f6b838b tcwg-update-llvmbot-containers.sh: Remove linaro-aarch64-flan [...]
adds 64bc662e1 tcwg-update-llvmbot-containers.sh: Remove linaro-aarch64-flan [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (99f6b838b)
\
N -- N -- N refs/changes/08/38708/2 (64bc662e1)
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.
No new revisions were added by this update.
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.
maxim.kuvyrkov pushed a change to reference refs/changes/08/38708/1
in repository toolchain/jenkins-scripts.
discards fc33e5ff3 tcwg-update-llvmbot-containers.sh: Remove linaro-aarch64-flan [...]
new 367977c01 tcwg-update-llvmbot-containers.sh: Remove linaro-aarch64-flan [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (fc33e5ff3)
\
N -- N -- N refs/changes/08/38708/1 (367977c01)
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 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:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/08/35308/5
in repository toolchain/jenkins-scripts.
discards b5a367d78 twcg_bmk-build.sh: Correct scope of build ret
adds dbbb8b845 twcg_bmk-build.sh: Correct scope of build ret
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (b5a367d78)
\
N -- N -- N refs/changes/08/35308/5 (dbbb8b845)
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.
No new revisions were added by this update.
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.
maxim.kuvyrkov pushed a change to reference refs/changes/08/35308/4
in repository toolchain/jenkins-scripts.
discards c3397a37a twcg_bmk-build.sh: Correct scope of build ret
new 4edd2f98a twcg_bmk-build.sh: Correct scope of build ret
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (c3397a37a)
\
N -- N -- N refs/changes/08/35308/4 (4edd2f98a)
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 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:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/08/35308/3
in repository toolchain/jenkins-scripts.
discards 1b00ac6ba twcg_bmk-build.sh: Correct build_ret undefined
new fb7d1698f twcg_bmk-build.sh: Correct build_ret undefined
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (1b00ac6ba)
\
N -- N -- N refs/changes/08/35308/3 (fb7d1698f)
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 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:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/08/35308/2
in repository toolchain/jenkins-scripts.
discards 3197f01b2 twcg_bmk-build.sh: Correct build_ret undefined
new 907d85d7d twcg_bmk-build.sh: Correct build_ret undefined
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (3197f01b2)
\
N -- N -- N refs/changes/08/35308/2 (907d85d7d)
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 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:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/08/35308/1
in repository toolchain/jenkins-scripts.
discards c2c162fae twcg_bmk-build.sh: Correct scope of build_ret var
new d42257dbd twcg_bmk-build.sh: Correct scope of build_ret var
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (c2c162fae)
\
N -- N -- N refs/changes/08/35308/1 (d42257dbd)
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 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:
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/08/32908/1
in repository toolchain/jenkins-scripts.
discards 6058e0a6a tcwg-update-llvmbot-containers.sh: Follow-up fix
adds 894e7d75e tcwg-update-llvmbot-containers.sh: Follow-up fix
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (6058e0a6a)
\
N -- N -- N refs/changes/08/32908/1 (894e7d75e)
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.
No new revisions were added by this update.
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.
maxim.kuvyrkov pushed a change to reference refs/changes/08/29908/3
in repository toolchain/jenkins-scripts.
discards 3323a9727 tcwg_kernel-bisect.sh: Don't force $reproduce_bisect==true in [...]
discards 3fc310049 tcwg-benchmark.sh: Add support for :parallelize parameter in [...]
adds a4061179b tcwg-benchmark.sh: Add support for :parallelize parameter in [...]
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (3323a9727)
\
N -- N -- N refs/changes/08/29908/3 (a4061179b)
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.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 397 --------------------------------------------------
1 file changed, 397 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
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.
maxim.kuvyrkov pushed a change to reference refs/changes/08/29908/2
in repository toolchain/jenkins-scripts.
discards c84313119 tcwg_kernel-bisect.sh: Don't force $reproduce_bisect==true in [...]
discards 564022aa3 tcwg_kernel-bisect.sh: Better handle regressions in merge commits
discards 6de8c98b4 tcwg_kernel-bisect.sh: Avoid absolute paths in manifests
adds 4f8d0638d tcwg_kernel-bisect.sh: Avoid absolute paths in manifests
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
reference 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 (c84313119)
\
N -- N -- N refs/changes/08/29908/2 (4f8d0638d)
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.
No new revisions were added by this update.
Summary of changes:
tcwg_kernel-bisect.sh | 397 --------------------------------------------------
1 file changed, 397 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.