This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/09/29909/2
in repository toolchain/jenkins-scripts.
discards 9f60df151 tcwg_kernel-bisect.sh: Simplify checking first_bad's parents
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 (9f60df151)
\
N -- N -- N refs/changes/09/29909/2 (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 | 387 --------------------------------------------------
1 file changed, 387 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/09/29909/1
in repository toolchain/jenkins-scripts.
discards e05365667 tcwg_kernel-bisect.sh: Simplify checking first_bad's parents
discards 496d0d8cf 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 (e05365667)
\
N -- N -- N refs/changes/09/29909/1 (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 | 387 --------------------------------------------------
1 file changed, 387 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/09/29409/3
in repository toolchain/jenkins-scripts.
discards 57c1064e5 tcwg_kernel*: Rename config[*] to rr[*].
adds 008da0cd7 tcwg_kernel*: Rename config[*] to rr[*].
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 (57c1064e5)
\
N -- N -- N refs/changes/09/29409/3 (008da0cd7)
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/09/29409/2
in repository toolchain/jenkins-scripts.
discards 4627c9d34 tcwg_kernel*: Rename config[*] to rr[*].
adds b9cc68c4d tcwg_kernel*: Rename config[*] to rr[*].
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 (4627c9d34)
\
N -- N -- N refs/changes/09/29409/2 (b9cc68c4d)
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/09/29409/1
in repository toolchain/jenkins-scripts.
discards 749a1e5f9 tcwg_kernel*: Rename config[*] to rr[*].
new 77f599e7e tcwg_kernel*: Rename config[*] to rr[*].
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 (749a1e5f9)
\
N -- N -- N refs/changes/09/29409/1 (77f599e7e)
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/47208/2
in repository toolchain/jenkins-scripts.
discards d5553b2d1 round-robin.sh (build_abe): Use ABE's --force_build
adds bb702a7c1 round-robin.sh (build_abe): Use ABE's --force_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 (d5553b2d1)
\
N -- N -- N refs/changes/08/47208/2 (bb702a7c1)
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/47208/1
in repository toolchain/jenkins-scripts.
discards 62ceda0af round-robin.sh (build_abe): Use ABE's --force_build
new d80b4758f round-robin.sh (build_abe): Use ABE's --force_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 (62ceda0af)
\
N -- N -- N refs/changes/08/47208/1 (d80b4758f)
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/46908/1
in repository toolchain/jenkins-scripts.
discards 5749abc29 tcwg_chromium-build.sh: Try another fix for package keyboard- [...]
adds 7a672969d tcwg_chromium-build.sh: Try another fix for package keyboard- [...]
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 (5749abc29)
\
N -- N -- N refs/changes/08/46908/1 (7a672969d)
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/46608/5
in repository toolchain/jenkins-scripts.
discards 249dde407 round-robin.sh (build_abe) Enable maintainer_mode in precommi [...]
adds 754cb2866 round-robin.sh (build_abe) Enable maintainer_mode in precommi [...]
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 (249dde407)
\
N -- N -- N refs/changes/08/46608/5 (754cb2866)
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/46608/4
in repository toolchain/jenkins-scripts.
discards 9159c988a round-robin.sh (build_abe) Enable maintainer_mode in precommi [...]
adds 81b26c3ac round-robin.sh (build_abe) Enable maintainer_mode in precommi [...]
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 (9159c988a)
\
N -- N -- N refs/changes/08/46608/4 (81b26c3ac)
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.