This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/34/30934/1
in repository toolchain/jenkins-scripts.
discards be240c9d7 round-robin-bisect.sh: Fix get_first_bad
discards 2fd1e2bcf docker-run.sh, jenkins-helpers.sh: Fix use of flock
adds fd1c5787b docker-run.sh, jenkins-helpers.sh: Fix use of flock
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 (be240c9d7)
\
N -- N -- N refs/changes/34/30934/1 (fd1c5787b)
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-bisect.sh | 484 --------------------------------------------------
1 file changed, 484 deletions(-)
delete mode 100755 round-robin-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/34/29834/3
in repository toolchain/jenkins-scripts.
discards a61032cab jenkins-helpers.sh: Fix fresh_dir and use it in git_clean
adds 8df505b4c jenkins-helpers.sh: Fix fresh_dir and use it in git_clean
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 (a61032cab)
\
N -- N -- N refs/changes/34/29834/3 (8df505b4c)
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/34/29834/2
in repository toolchain/jenkins-scripts.
discards b98b781c4 jenkins-helpers.sh: Fix fresh_dir and use it in git_clean
adds 97a2cbe8b jenkins-helpers.sh: Fix fresh_dir and use it in git_clean
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 (b98b781c4)
\
N -- N -- N refs/changes/34/29834/2 (97a2cbe8b)
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/34/29834/1
in repository toolchain/jenkins-scripts.
discards 7fb0751a8 jenkins-helpers.sh: Fix fresh_dir and use it in git_clean
adds 0e10f2522 jenkins-helpers.sh: Fix fresh_dir and use it in git_clean
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 (7fb0751a8)
\
N -- N -- N refs/changes/34/29834/1 (0e10f2522)
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/34/29434/2
in repository toolchain/jenkins-scripts.
discards a7561ca7a tcwg_kernel-build.sh: Document ${rr[]} elements
adds 0333e84f4 tcwg_kernel-build.sh: Document ${rr[]} elements
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 (a7561ca7a)
\
N -- N -- N refs/changes/34/29434/2 (0333e84f4)
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/34/29434/1
in repository toolchain/jenkins-scripts.
discards 51de451df tcwg_kernel-build.sh: Document ${rr[]} elements
new 2d81979d2 tcwg_kernel-build.sh: Document ${rr[]} elements
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 (51de451df)
\
N -- N -- N refs/changes/34/29434/1 (2d81979d2)
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/33/47033/3
in repository toolchain/jenkins-scripts.
discards 9a892d128 tcwg_chromium-build.sh: temporary fix for dep_url
adds 63b3e3fc1 tcwg_chromium-build.sh: temporary fix for dep_url
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 (9a892d128)
\
N -- N -- N refs/changes/33/47033/3 (63b3e3fc1)
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/33/47033/2
in repository toolchain/jenkins-scripts.
discards ed358d221 tcwg_chromium-build.sh: temporary fix for dep_url
new 255907ec2 tcwg_chromium-build.sh: temporary fix for dep_url
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 (ed358d221)
\
N -- N -- N refs/changes/33/47033/2 (255907ec2)
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/33/47033/1
in repository toolchain/jenkins-scripts.
discards e6c0ffc14 tcwg_chromium-build.sh: temporary fix for dep_url
new 529551ca1 tcwg_chromium-build.sh: temporary fix for dep_url
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 (e6c0ffc14)
\
N -- N -- N refs/changes/33/47033/1 (529551ca1)
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/33/46933/2
in repository toolchain/jenkins-scripts.
discards 8281cc911 tcwg_chromium-build.sh: skip some parts to debug
adds 4cc55a7f2 tcwg_chromium-build.sh: skip some parts to debug
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 (8281cc911)
\
N -- N -- N refs/changes/33/46933/2 (4cc55a7f2)
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.