This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/03/29403/2
in repository toolchain/jenkins-scripts.
discards ac152c3d6 convert_args_to_variables: Rework handling of configuration v [...]
adds 0df6c2bac convert_args_to_variables: Rework handling of configuration v [...]
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 (ac152c3d6)
\
N -- N -- N refs/changes/03/29403/2 (0df6c2bac)
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/03/29403/1
in repository toolchain/jenkins-scripts.
discards be916b52a convert_args_to_variables: Rework handling of configuration v [...]
adds 2d0dcc2bd convert_args_to_variables: Rework handling of configuration v [...]
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 (be916b52a)
\
N -- N -- N refs/changes/03/29403/1 (2d0dcc2bd)
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/02/47302/1
in repository toolchain/jenkins-scripts.
discards b2ef441e3 round-robin-notify.sh: fetching tags if needed
discards 251f4858b tcwg-benchmark-results.sh: status_csv passed to interesting s [...]
adds 4a8c24605 tcwg-benchmark-results.sh: status_csv passed to interesting s [...]
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 (b2ef441e3)
\
N -- N -- N refs/changes/02/47302/1 (4a8c24605)
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 | 650 -------------
round-robin-bisect.sh | 735 --------------
round-robin-notify.sh | 2429 -----------------------------------------------
3 files changed, 3814 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/02/47202/1
in repository toolchain/jenkins-scripts.
discards 638a9f04b tcwg_chromium-build.sh: rr[xxx_git] now accept a branch, a re [...]
adds 550d03d50 tcwg_chromium-build.sh: rr[xxx_git] now accept a branch, a re [...]
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 (638a9f04b)
\
N -- N -- N refs/changes/02/47202/1 (550d03d50)
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/02/47102/5
in repository toolchain/jenkins-scripts.
discards c1883aaf9 round-robin-baseline.sh: Only need major and minor revision t [...]
adds 8e2331655 round-robin-baseline.sh: Only need major and minor revision t [...]
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 (c1883aaf9)
\
N -- N -- N refs/changes/02/47102/5 (8e2331655)
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/02/47102/4
in repository toolchain/jenkins-scripts.
discards d612d239c round-robin-baseline.sh: Only need major and minor revision t [...]
new 4cb618b56 round-robin-baseline.sh: Only need major and minor revision t [...]
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 (d612d239c)
\
N -- N -- N refs/changes/02/47102/4 (4cb618b56)
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/02/47102/3
in repository toolchain/jenkins-scripts.
discards 53a88b255 round-robin-baseline.sh,round-robin.sh: A rewrite-baseline is [...]
new 8f08a1804 round-robin-baseline.sh,round-robin.sh: A rewrite-baseline is [...]
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 (53a88b255)
\
N -- N -- N refs/changes/02/47102/3 (8f08a1804)
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/02/47102/2
in repository toolchain/jenkins-scripts.
discards 45f9fb7bf round-robin-baseline.sh,round-robin.sh: rewrite baseline canb [...]
new 2221ecf77 round-robin-baseline.sh,round-robin.sh: rewrite baseline canb [...]
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 (45f9fb7bf)
\
N -- N -- N refs/changes/02/47102/2 (2221ecf77)
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/02/47102/1
in repository toolchain/jenkins-scripts.
discards b75d83c20 round-robin-baseline.sh,round-robin.sh: rewrite baseline canb [...]
new be5b86eb4 round-robin-baseline.sh,round-robin.sh: rewrite baseline canb [...]
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 (b75d83c20)
\
N -- N -- N refs/changes/02/47102/1 (be5b86eb4)
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/02/47002/5
in repository toolchain/jenkins-scripts.
discards c66738992 round-robin.sh (build_abe): Build docs in build-ony jobs
adds f1576973f round-robin.sh (build_abe): Build docs in build-ony jobs
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 (c66738992)
\
N -- N -- N refs/changes/02/47002/5 (f1576973f)
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.