This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/82/29882/4
in repository toolchain/jenkins-scripts.
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 (564022aa3)
\
N -- N -- N refs/changes/82/29882/4 (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 | 403 --------------------------------------------------
1 file changed, 403 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/82/29882/3
in repository toolchain/jenkins-scripts.
discards e47ffe62f tcwg_kernel-bisect.sh: Better handle regressions in merge commits
discards e0b5b8901 tcwg_kernel-bisect.sh: Avoid absolute paths in manifests
new 444754f14 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 (e47ffe62f)
\
N -- N -- N refs/changes/82/29882/3 (444754f14)
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 | 403 --------------------------------------------------
1 file changed, 403 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/82/29882/2
in repository toolchain/jenkins-scripts.
discards 148a356dd tcwg_kernel-bisect.sh: Better handle regressions in merges commits
discards e0b5b8901 tcwg_kernel-bisect.sh: Avoid absolute paths in manifests
new 444754f14 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 (148a356dd)
\
N -- N -- N refs/changes/82/29882/2 (444754f14)
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 | 403 --------------------------------------------------
1 file changed, 403 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/82/29882/1
in repository toolchain/jenkins-scripts.
discards 3148df583 tcwg_kernel-bisect.sh: Better handle regressions in merges commits
discards bc4325fac tcwg_kernel-bisect.sh: Avoid absolute paths in manifests
new ad9e3b2d2 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 (3148df583)
\
N -- N -- N refs/changes/82/29882/1 (ad9e3b2d2)
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 | 403 --------------------------------------------------
1 file changed, 403 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/81/47281/1
in repository toolchain/jenkins-scripts.
discards dc3a080c2 tcwg_chromium-build.sh,ci-autotest.sh: depot_tools_init is pa [...]
adds 1fc1112cb tcwg_chromium-build.sh,ci-autotest.sh: depot_tools_init is pa [...]
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 (dc3a080c2)
\
N -- N -- N refs/changes/81/47281/1 (1fc1112cb)
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/81/47181/1
in repository toolchain/jenkins-scripts.
discards 237f5e4a7 tcwg_chromium-build.sh: launch only one setdep command
adds 37fd01d0b tcwg_chromium-build.sh: launch only one setdep command
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 (237f5e4a7)
\
N -- N -- N refs/changes/81/47181/1 (37fd01d0b)
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/81/46981/3
in repository toolchain/jenkins-scripts.
discards 4e349c6c6 tcwg-lnt: Filter the json inputs for each server
adds 971f4dac3 tcwg-lnt: Filter the json inputs for each server
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 (4e349c6c6)
\
N -- N -- N refs/changes/81/46981/3 (971f4dac3)
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/81/46981/2
in repository toolchain/jenkins-scripts.
discards c85d44777 tcwg-lnt: Filter the json inputs for each server
new a719f26c6 tcwg-lnt: Filter the json inputs for each server
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 (c85d44777)
\
N -- N -- N refs/changes/81/46981/2 (a719f26c6)
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/81/46981/1
in repository toolchain/jenkins-scripts.
discards 842821600 tcwg-lnt: Filter the json inputs for each server
new 16af8b216 tcwg-lnt: Filter the json inputs for each server
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 (842821600)
\
N -- N -- N refs/changes/81/46981/1 (16af8b216)
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/81/46681/1
in repository toolchain/jenkins-scripts.
discards ee9a98bdd Partially revert previous commit
adds 59bbc113b Partially revert previous commit
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 (ee9a98bdd)
\
N -- N -- N refs/changes/81/46681/1 (59bbc113b)
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.