This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/77/29377/5
in repository toolchain/jenkins-scripts.
discards 5d1de6f17 tcwg_kernel-build.sh: Support building glibc and gcc-stage2
adds c65a1bfa5 tcwg_kernel-build.sh: Support building glibc and gcc-stage2
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 (5d1de6f17)
\
N -- N -- N refs/changes/77/29377/5 (c65a1bfa5)
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/77/29377/4
in repository toolchain/jenkins-scripts.
discards b2ed63160 tcwg_kernel-build.sh: Support building glibc and gcc-stage2
adds 6effabfbc tcwg_kernel-build.sh: Support building glibc and gcc-stage2
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 (b2ed63160)
\
N -- N -- N refs/changes/77/29377/4 (6effabfbc)
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/77/29377/3
in repository toolchain/jenkins-scripts.
discards 63f0c21dc tcwg_kernel-build.sh: Support building glibc and gcc-stage2
adds b4dc56ce2 tcwg_kernel-build.sh: Support building glibc and gcc-stage2
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 (63f0c21dc)
\
N -- N -- N refs/changes/77/29377/3 (b4dc56ce2)
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/77/29377/2
in repository toolchain/jenkins-scripts.
discards c2d5d6866 tcwg_kernel-build.sh: Support building glibc and gcc-stage2
adds 0326ea157 tcwg_kernel-build.sh: Support building glibc and gcc-stage2
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 (c2d5d6866)
\
N -- N -- N refs/changes/77/29377/2 (0326ea157)
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/77/29377/1
in repository toolchain/jenkins-scripts.
discards 0e1137eb3 tcwg_kernel-build.sh: Support building glibc and gcc-stage2
adds ca4fcc9ec tcwg_kernel-build.sh: Support building glibc and gcc-stage2
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 (0e1137eb3)
\
N -- N -- N refs/changes/77/29377/1 (ca4fcc9ec)
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/76/46876/3
in repository toolchain/jenkins-scripts.
discards b3ab1d268 tcwg-update-bmk-containers.sh: power-cycle the bmk board if n [...]
adds 2ceb47d76 tcwg-update-bmk-containers.sh: power-cycle the bmk board if n [...]
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 (b3ab1d268)
\
N -- N -- N refs/changes/76/46876/3 (2ceb47d76)
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/76/46876/2
in repository toolchain/jenkins-scripts.
discards 33fe2cba1 tcwg-update-bmk-containers.sh: power-cycle the bmk board if n [...]
new 69b21b226 tcwg-update-bmk-containers.sh: power-cycle the bmk board if n [...]
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 (33fe2cba1)
\
N -- N -- N refs/changes/76/46876/2 (69b21b226)
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/76/46876/1
in repository toolchain/jenkins-scripts.
discards 7967a9b8c tcwg-update-bmk-containers.sh: power-cycle the bmk board if n [...]
new 60c82762d tcwg-update-bmk-containers.sh: power-cycle the bmk board if n [...]
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 (7967a9b8c)
\
N -- N -- N refs/changes/76/46876/1 (60c82762d)
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/76/45676/1
in repository toolchain/jenkins-scripts.
discards 7a5971879 round-robin-notify.sh: Fix bmk_generate_extra_details
discards 08db330b1 tcwg_bmk-build.sh: Test history rewrite on SPEC CPU2006 configs
adds 0c9f4f98d tcwg_bmk-build.sh: Test history rewrite on SPEC CPU2006 configs
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 (7a5971879)
\
N -- N -- N refs/changes/76/45676/1 (0c9f4f98d)
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 | 477 -------------
round-robin-bisect.sh | 655 ------------------
round-robin-notify.sh | 1759 -----------------------------------------------
3 files changed, 2891 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.
This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/76/44876/1
in repository toolchain/jenkins-scripts.
discards 471679a8f tcwg-benchmark-results.sh: Fix when using local dir
adds 023d79fc0 tcwg-benchmark-results.sh: Fix when using local dir
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 (471679a8f)
\
N -- N -- N refs/changes/76/44876/1 (023d79fc0)
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.