This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/26/37726/1
in repository toolchain/jenkins-scripts.
discards 746f4c6a9 tcwg_bmk-build.sh: Fix failure when bisecting glibc across releases
adds 3b6f31e34 tcwg_bmk-build.sh: Fix failure when bisecting glibc across releases
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 (746f4c6a9)
\
N -- N -- N refs/changes/26/37726/1 (3b6f31e34)
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/26/37526/1
in repository toolchain/jenkins-scripts.
discards 5159cbddd tcwg_bmk-build.sh: Don't use --with-mode=thumb for arm-eabi
adds 5c362b6bb tcwg_bmk-build.sh: Don't use --with-mode=thumb for arm-eabi
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 (5159cbddd)
\
N -- N -- N refs/changes/26/37526/1 (5c362b6bb)
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/26/34026/2
in repository toolchain/jenkins-scripts.
discards 377eba35c round-robin-bisect.sh: Update after split of tcwg_bmk
discards 31272ab9a tcwg_bmk-build.sh: Update display tag of benchmark jobs
adds 190adca10 tcwg_bmk-build.sh: Update display tag of benchmark jobs
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 (377eba35c)
\
N -- N -- N refs/changes/26/34026/2 (190adca10)
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:
round-robin-bisect.sh | 598 --------------------------------------------------
1 file changed, 598 deletions(-)
delete mode 100755 round-robin-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/26/34026/1
in repository toolchain/jenkins-scripts.
discards a1faea8e3 round-robin-bisect.sh: Update after split of tcwg_bmk
discards 89e905ed5 round-robin-bisect.sh: Better handle skipping of "bad" build
discards 31272ab9a tcwg_bmk-build.sh: Update display tag of benchmark jobs
adds 190adca10 tcwg_bmk-build.sh: Update display tag of benchmark jobs
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 (a1faea8e3)
\
N -- N -- N refs/changes/26/34026/1 (190adca10)
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:
round-robin-bisect.sh | 604 --------------------------------------------------
1 file changed, 604 deletions(-)
delete mode 100755 round-robin-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/26/30526/2
in repository toolchain/jenkins-scripts.
discards 849ca36d4 tcwg_bmk-build.sh: Fetch bmk results_id from artifacts
adds c3affc54a tcwg_bmk-build.sh: Fetch bmk results_id from artifacts
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 (849ca36d4)
\
N -- N -- N refs/changes/26/30526/2 (c3affc54a)
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/26/30526/1
in repository toolchain/jenkins-scripts.
discards 1286e97d8 tcwg_bmk-build.sh: Fetch bmk results_id from artifacts
adds 5413cde1a tcwg_bmk-build.sh: Fetch bmk results_id from artifacts
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 (1286e97d8)
\
N -- N -- N refs/changes/26/30526/1 (5413cde1a)
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/26/30426/1
in repository toolchain/jenkins-scripts.
discards fb082dee1 tcwg_bmk-build.sh: Avoid aliasing of benchmarking results
adds f6018f16d tcwg_bmk-build.sh: Avoid aliasing of benchmarking results
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 (fb082dee1)
\
N -- N -- N refs/changes/26/30426/1 (f6018f16d)
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/26/29726/2
in repository toolchain/jenkins-scripts.
discards dee30002a tcwg_kernel-bisect.sh: Fix handling of manifest files
discards 9bb3a33d9 tcwg_kernel-bisect.sh: Add support to reproduce bisects.
adds 81b830c9b tcwg_kernel-bisect.sh: Add support to reproduce bisects.
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 (dee30002a)
\
N -- N -- N refs/changes/26/29726/2 (81b830c9b)
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 | 376 --------------------------------------------------
1 file changed, 376 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/26/29726/1
in repository toolchain/jenkins-scripts.
discards 48cddc071 tcwg_kernel-bisect.sh: Fix handling of manifest files
discards 15d6ee051 tcwg_kernel-bisect.sh: Add support to reproduce bisects.
new 4aac3d310 tcwg_kernel-bisect.sh: Add support to reproduce bisects.
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 (48cddc071)
\
N -- N -- N refs/changes/26/29726/1 (4aac3d310)
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:
tcwg_kernel-bisect.sh | 376 --------------------------------------------------
1 file changed, 376 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/25/47325/2
in repository toolchain/jenkins-scripts.
discards 49dc24809 round-robin-notify.sh: Replace "progression" with "improvement"
discards bc3441401 Revert "tcwg-update-llvmbot-containers: Move Arm lldb bot to silent"
adds 8437865af Revert "tcwg-update-llvmbot-containers: Move Arm lldb bot to silent"
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 (49dc24809)
\
N -- N -- N refs/changes/25/47325/2 (8437865af)
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:
round-robin-baseline.sh | 650 -------------
round-robin-bisect.sh | 735 --------------
round-robin-notify.sh | 2429 -----------------------------------------------
3 files changed, 3814 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.