This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/20/31220/2
in repository toolchain/jenkins-scripts.
discards 3fffc3073 jenkins-helpers.sh: Generalize clone_or_update_repo*
adds e2c6e0326 jenkins-helpers.sh: Generalize clone_or_update_repo*
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 (3fffc3073)
\
N -- N -- N refs/changes/20/31220/2 (e2c6e0326)
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/20/31220/1
in repository toolchain/jenkins-scripts.
discards c930f36dc jenkins-helpers.sh: Generalize clone_or_update_repo*
adds 309f87047 jenkins-helpers.sh: Generalize clone_or_update_repo*
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 (c930f36dc)
\
N -- N -- N refs/changes/20/31220/1 (309f87047)
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/20/29820/1
in repository toolchain/jenkins-scripts.
discards 00370c419 TestRelease.job: execute all tests, update diagnostic format.
adds 6b5dacbce TestRelease.job: execute all tests, update diagnostic format.
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 (00370c419)
\
N -- N -- N refs/changes/20/29820/1 (6b5dacbce)
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/20/29620/2
in repository toolchain/jenkins-scripts.
discards b5cd9b277 jenkins-helpers.sh: Run "git gc" when updating git repos.
adds c85a9095a jenkins-helpers.sh: Run "git gc" when updating git repos.
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 (b5cd9b277)
\
N -- N -- N refs/changes/20/29620/2 (c85a9095a)
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/20/29620/1
in repository toolchain/jenkins-scripts.
discards 211379b39 jenkins-helpers.sh: Run "git gc" when updating git repos.
adds 7b773fb4a jenkins-helpers.sh: Run "git gc" when updating git repos.
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 (211379b39)
\
N -- N -- N refs/changes/20/29620/1 (7b773fb4a)
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/20/29420/2
in repository toolchain/jenkins-scripts.
discards 98c0bf194 tcwg_kernel-bisect.sh: Fix typo.
discards 7ab55d812 tcwg_kernel-bisect.sh: Update to use new format of "@@" inclu [...]
discards 508e1a638 jenkins-helpers.sh, tcwg-update-snapshots_ref.sh: Add tcwg-sq [...]
adds 18532311f jenkins-helpers.sh, tcwg-update-snapshots_ref.sh: Add tcwg-sq [...]
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 (98c0bf194)
\
N -- N -- N refs/changes/20/29420/2 (18532311f)
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 | 271 --------------------------------------------------
1 file changed, 271 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/20/29420/1
in repository toolchain/jenkins-scripts.
discards a26fb2569 tcwg_kernel-bisect.sh: Fix typo.
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 (a26fb2569)
\
N -- N -- N refs/changes/20/29420/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:
tcwg_kernel-bisect.sh | 261 --------------------------------------------------
1 file changed, 261 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/19/46919/1
in repository toolchain/jenkins-scripts.
discards 69b4267a5 tcwg_chromium-build.sh: Remove non necessary gclient sync
adds 483b3bcd6 tcwg_chromium-build.sh: Remove non necessary gclient sync
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 (69b4267a5)
\
N -- N -- N refs/changes/19/46919/1 (483b3bcd6)
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/19/46419/3
in repository toolchain/jenkins-scripts.
discards 8f2d7c630 round-robin.sh,tcwg_bmk-build.sh: Remove temporary code, used [...]
adds 695d1b872 round-robin.sh,tcwg_bmk-build.sh: Remove temporary code, used [...]
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 (8f2d7c630)
\
N -- N -- N refs/changes/19/46419/3 (695d1b872)
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/19/46419/2
in repository toolchain/jenkins-scripts.
discards 5c85d1f9e round-robin.sh,tcwg_bmk-build.sh: Remove temporary code, used [...]
adds f5edca080 round-robin.sh,tcwg_bmk-build.sh: Remove temporary code, used [...]
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 (5c85d1f9e)
\
N -- N -- N refs/changes/19/46419/2 (f5edca080)
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.