This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/27/45727/3
in repository toolchain/jenkins-scripts.
discards 261e54a0f round-robin-notify.sh (print_commits): Remove 'basepoints/' f [...]
discards 01a6434e3 generate-cimonitor-dashboard.py: Improve automatic diagnostic [...]
adds d01608255 generate-cimonitor-dashboard.py: Improve automatic diagnostic [...]
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 (261e54a0f)
\
N -- N -- N refs/changes/27/45727/3 (d01608255)
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 | 524 --------------
round-robin-bisect.sh | 681 ------------------
round-robin-notify.sh | 1808 -----------------------------------------------
3 files changed, 3013 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/27/45727/2
in repository toolchain/jenkins-scripts.
discards 8b70163e8 round-robin-notify.sh (print_commits): Remove 'basepoints/' f [...]
discards 01a6434e3 generate-cimonitor-dashboard.py: Improve automatic diagnostic [...]
adds d01608255 generate-cimonitor-dashboard.py: Improve automatic diagnostic [...]
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 (8b70163e8)
\
N -- N -- N refs/changes/27/45727/2 (d01608255)
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 | 524 --------------
round-robin-bisect.sh | 681 ------------------
round-robin-notify.sh | 1810 -----------------------------------------------
3 files changed, 3015 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/27/45727/1
in repository toolchain/jenkins-scripts.
discards 14e99f4a4 round-robin-notify.sh (print_commits): Remove 'basepoints/' f [...]
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 (14e99f4a4)
\
N -- N -- N refs/changes/27/45727/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 | 1763 -----------------------------------------------
3 files changed, 2895 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/27/44627/4
in repository toolchain/jenkins-scripts.
discards 5de5872b9 round-robin.sh (clone_repo): Remove unneeded manifest entries
adds e9b3dc151 round-robin.sh (clone_repo): Remove unneeded manifest entries
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 (5de5872b9)
\
N -- N -- N refs/changes/27/44627/4 (e9b3dc151)
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/27/44627/3
in repository toolchain/jenkins-scripts.
discards 5b16a378a round-robin.sh (clone_repo): Remove unneeded manifest entries
adds c1d4ac528 round-robin.sh (clone_repo): Remove unneeded manifest entries
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 (5b16a378a)
\
N -- N -- N refs/changes/27/44627/3 (c1d4ac528)
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/27/44627/2
in repository toolchain/jenkins-scripts.
discards be344b5f2 round-robin.sh (clone_repo): Remove unneeded manifest entries
adds 1634c5e26 round-robin.sh (clone_repo): Remove unneeded manifest entries
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 (be344b5f2)
\
N -- N -- N refs/changes/27/44627/2 (1634c5e26)
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/27/44627/1
in repository toolchain/jenkins-scripts.
discards 680eac835 round-robin.sh (clone_repo): Remove unneeded manifest entries
adds 3bdfdfaad round-robin.sh (clone_repo): Remove unneeded manifest entries
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 (680eac835)
\
N -- N -- N refs/changes/27/44627/1 (3bdfdfaad)
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/27/43527/1
in repository toolchain/jenkins-scripts.
discards d90a001b5 wrappers/shadow-ar.sh: Fix original AOSP build
adds 39b292723 wrappers/shadow-ar.sh: Fix original AOSP build
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 (d90a001b5)
\
N -- N -- N refs/changes/27/43527/1 (39b292723)
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/27/43427/1
in repository toolchain/jenkins-scripts.
discards ae761aae9 round-robin.sh (update_baseline): Fix rewrite of base-artifac [...]
adds 314c83698 round-robin.sh (update_baseline): Fix rewrite of base-artifac [...]
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 (ae761aae9)
\
N -- N -- N refs/changes/27/43427/1 (314c83698)
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/27/43327/2
in repository toolchain/jenkins-scripts.
discards b981a3550 tcwg-benchmark.sh: Fix reboot sequence
adds f1e09d411 tcwg-benchmark.sh: Fix reboot sequence
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 (b981a3550)
\
N -- N -- N refs/changes/27/43327/2 (f1e09d411)
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.