This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/30/29230/3
in repository toolchain/jenkins-scripts.
discards c91562084 Migrate email logic from tcwg_kernel.yaml to tcwg_kernel-bisect.sh.
discards 5cbd5427c tcwg_kernel-build.sh: Fix reset_artifacts to not delete artif [...]
adds 15bef0aa8 tcwg_kernel-build.sh: Fix reset_artifacts to not delete artif [...]
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 (c91562084)
\
N -- N -- N refs/changes/30/29230/3 (15bef0aa8)
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 | 223 --------------------------------------------------
1 file changed, 223 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/30/29230/2
in repository toolchain/jenkins-scripts.
discards a4579bf51 Migrate email logic from tcwg_kernel.yaml to tcwg_kernel-bisect.sh.
discards 5cbd5427c tcwg_kernel-build.sh: Fix reset_artifacts to not delete artif [...]
adds 15bef0aa8 tcwg_kernel-build.sh: Fix reset_artifacts to not delete artif [...]
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 (a4579bf51)
\
N -- N -- N refs/changes/30/29230/2 (15bef0aa8)
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 | 222 --------------------------------------------------
1 file changed, 222 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/30/29230/1
in repository toolchain/jenkins-scripts.
discards 951953e27 Migrate email logic from tcwg_kernel.yaml to tcwg_kernel-bisect.sh.
discards 5cbd5427c tcwg_kernel-build.sh: Fix reset_artifacts to not delete artif [...]
adds 15bef0aa8 tcwg_kernel-build.sh: Fix reset_artifacts to not delete artif [...]
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 (951953e27)
\
N -- N -- N refs/changes/30/29230/1 (15bef0aa8)
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 | 222 --------------------------------------------------
1 file changed, 222 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/29/47229/3
in repository toolchain/jenkins-scripts.
discards b455e753d round-robin-notify.sh: proper config specific initialization. [...]
discards 4bde48ce0 pw-helpers.sh (pw_patch_check_state): Handle multi-page "chec [...]
adds 64d6faf6c pw-helpers.sh (pw_patch_check_state): Handle multi-page "chec [...]
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 (b455e753d)
\
N -- N -- N refs/changes/29/47229/3 (64d6faf6c)
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 | 669 -------------
round-robin-bisect.sh | 744 ---------------
round-robin-notify.sh | 2416 -----------------------------------------------
3 files changed, 3829 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/29/47229/2
in repository toolchain/jenkins-scripts.
discards b28961db0 round-robin-notify.sh: proper config specific initialization. [...]
discards 0f44b6c2b tcwg_chromium-build.sh: gclient sync is needed even in fast_demo
adds a3370bef4 tcwg_chromium-build.sh: gclient sync is needed even in fast_demo
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 (b28961db0)
\
N -- N -- N refs/changes/29/47229/2 (a3370bef4)
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 | 669 -------------
round-robin-bisect.sh | 744 ---------------
round-robin-notify.sh | 2416 -----------------------------------------------
3 files changed, 3829 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/29/47229/1
in repository toolchain/jenkins-scripts.
discards 4f8ab5240 round-robin-notify.sh: proper config specific initialization. [...]
discards 0f44b6c2b tcwg_chromium-build.sh: gclient sync is needed even in fast_demo
adds a3370bef4 tcwg_chromium-build.sh: gclient sync is needed even in fast_demo
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 (4f8ab5240)
\
N -- N -- N refs/changes/29/47229/1 (a3370bef4)
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 | 669 -------------
round-robin-bisect.sh | 744 ---------------
round-robin-notify.sh | 2419 -----------------------------------------------
3 files changed, 3832 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/29/47129/1
in repository toolchain/jenkins-scripts.
discards 9cc22dba8 tcwg_bmk-build.sh: Add baseline annex download during check_r [...]
adds 3dbd6cb07 tcwg_bmk-build.sh: Add baseline annex download during check_r [...]
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 (9cc22dba8)
\
N -- N -- N refs/changes/29/47129/1 (3dbd6cb07)
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/29/47029/2
in repository toolchain/jenkins-scripts.
discards 4fac2024c tcwg-lnt/create-server.sh: Remove database on schema change
adds 91acf1fd7 tcwg-lnt/create-server.sh: Remove database on schema change
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 (4fac2024c)
\
N -- N -- N refs/changes/29/47029/2 (91acf1fd7)
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/29/47029/1
in repository toolchain/jenkins-scripts.
discards f4ab841ff tcwg-lnt/create-server.sh: Remove database on schema change
adds dffb04c16 tcwg-lnt/create-server.sh: Remove database on schema change
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 (f4ab841ff)
\
N -- N -- N refs/changes/29/47029/1 (dffb04c16)
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/29/46929/2
in repository toolchain/jenkins-scripts.
discards 4b11d7e98 pw-helpers.sh (apply_series_with_retry): Try 3 ways of applyi [...]
adds 57b3a2007 pw-helpers.sh (apply_series_with_retry): Try 3 ways of applyi [...]
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 (4b11d7e98)
\
N -- N -- N refs/changes/29/46929/2 (57b3a2007)
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.