This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/24/29724/1
in repository toolchain/jenkins-scripts.
discards 5a8466bd6 tcwg_kernel-bisect.sh: Handle git-bisect's smartness.
discards 60d138622 tcwg_kernel-bisect.sh: Add support to reproduce bisects.
discards 1f4200537 tcwg_kernel-bisect.sh: Try harder to bisect linux-next failures
discards 46c2519e1 tcwg_kernel-bisect.sh: Cleanup.
discards fa931307a tcwg_kernel-bisect.sh: Send emails with useful info when bise [...]
discards f238c3d99 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
adds de5d2bdf3 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
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 (5a8466bd6)
\
N -- N -- N refs/changes/24/29724/1 (de5d2bdf3)
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 | 365 --------------------------------------------------
1 file changed, 365 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/24/29624/2
in repository toolchain/jenkins-scripts.
discards 1f4200537 tcwg_kernel-bisect.sh: Try harder to bisect linux-next failures
discards 46c2519e1 tcwg_kernel-bisect.sh: Cleanup.
discards fa931307a tcwg_kernel-bisect.sh: Send emails with useful info when bise [...]
discards f238c3d99 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
adds de5d2bdf3 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
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 (1f4200537)
\
N -- N -- N refs/changes/24/29624/2 (de5d2bdf3)
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 | 330 --------------------------------------------------
1 file changed, 330 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/24/29624/1
in repository toolchain/jenkins-scripts.
discards 4e2d05b95 tcwg_kernel-bisect.sh: Try harder to bisect linux-next failures
discards f294c203e tcwg_kernel-bisect.sh: Cleanup.
discards 801040254 tcwg_kernel-bisect.sh: Send emails with useful info when bise [...]
discards 38a883d64 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
adds 75c9233c3 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
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 (4e2d05b95)
\
N -- N -- N refs/changes/24/29624/1 (75c9233c3)
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 | 330 --------------------------------------------------
1 file changed, 330 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/24/29424/2
in repository toolchain/jenkins-scripts.
discards ed75b2f2d tcwg_kernel*: Rename git_repo and git_branch
adds 0b9950eee tcwg_kernel*: Rename git_repo and git_branch
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 (ed75b2f2d)
\
N -- N -- N refs/changes/24/29424/2 (0b9950eee)
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/24/29424/1
in repository toolchain/jenkins-scripts.
discards 8a69379ea tcwg_kernel*: Rename git_repo and git_branch
adds c09f4655d tcwg_kernel*: Rename git_repo and git_branch
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 (8a69379ea)
\
N -- N -- N refs/changes/24/29424/1 (c09f4655d)
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/23/47323/1
in repository toolchain/jenkins-scripts.
discards 421f3b3e3 tcwg_chromium-config.sh: cidemo only change for rr_stage=build
adds b8b3e9b5f tcwg_chromium-config.sh: cidemo only change for rr_stage=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 (421f3b3e3)
\
N -- N -- N refs/changes/23/47323/1 (b8b3e9b5f)
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/23/47123/1
in repository toolchain/jenkins-scripts.
discards ee7ec2fec tcwg-start-container.sh (keep_existing): Change default to ke [...]
adds c2bd70ad0 tcwg-start-container.sh (keep_existing): Change default to ke [...]
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 (ee7ec2fec)
\
N -- N -- N refs/changes/23/47123/1 (c2bd70ad0)
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/23/47023/2
in repository toolchain/jenkins-scripts.
discards 8cd0a913f tcwg-cleanup-stale-results.sh: Don't hard-code user $HOME
adds c69564d16 tcwg-cleanup-stale-results.sh: Don't hard-code user $HOME
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 (8cd0a913f)
\
N -- N -- N refs/changes/23/47023/2 (c69564d16)
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/23/47023/1
in repository toolchain/jenkins-scripts.
discards f3654b1cd tcwg-cleanup-stale-results.sh: Don't hard-code user $HOME
new 356b72aac tcwg-cleanup-stale-results.sh: Don't hard-code user $HOME
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 (f3654b1cd)
\
N -- N -- N refs/changes/23/47023/1 (356b72aac)
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/23/46923/2
in repository toolchain/jenkins-scripts.
discards 175ea2b4a tcwg_chromium-build.sh: Fix check_regression
adds da5b32f56 tcwg_chromium-build.sh: Fix check_regression
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 (175ea2b4a)
\
N -- N -- N refs/changes/23/46923/2 (da5b32f56)
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.