This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/77/39177/1
in repository toolchain/jenkins-scripts.
discards 15367ef8d round-robin-bisect.sh: Fix quoting
discards 8e8b037ae round-robin-bisect.sh: Update email preferences
discards 9b02eebd5 round-robin-bisect.sh: Fix line breaks
discards e599832c4 round-robin-bisect.sh: Save/restore baseline state
adds 6d14ec972 round-robin-bisect.sh: Save/restore baseline state
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 (15367ef8d)
\
N -- N -- N refs/changes/77/39177/1 (6d14ec972)
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 | 782 --------------------------------------------------
1 file changed, 782 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/77/38977/1
in repository toolchain/jenkins-scripts.
discards 472672bdc tcwg-generate-source-cache.sh: Cleanup and prepare for bmk ca [...]
adds 8b0a2e3e6 tcwg-generate-source-cache.sh: Cleanup and prepare for bmk ca [...]
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 (472672bdc)
\
N -- N -- N refs/changes/77/38977/1 (8b0a2e3e6)
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/77/37977/2
in repository toolchain/jenkins-scripts.
discards 32b38c482 tcwg-benchmark-bare.sh: Fix toolchain copy via rsync
adds 6c706de51 tcwg-benchmark-bare.sh: Fix toolchain copy via rsync
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 (32b38c482)
\
N -- N -- N refs/changes/77/37977/2 (6c706de51)
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/77/37977/1
in repository toolchain/jenkins-scripts.
discards a87e6ce9c tcwg-benchmark-bare.sh: Fix toolchain copy via rsync
new f21b2ba28 tcwg-benchmark-bare.sh: Fix toolchain copy via rsync
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 (a87e6ce9c)
\
N -- N -- N refs/changes/77/37977/1 (f21b2ba28)
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/77/37377/3
in repository toolchain/jenkins-scripts.
discards 50781c0bd Reduce "docker pull" requests to dockerhub
adds f6ddf1f01 Reduce "docker pull" requests to dockerhub
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 (50781c0bd)
\
N -- N -- N refs/changes/77/37377/3 (f6ddf1f01)
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/77/37377/2
in repository toolchain/jenkins-scripts.
discards 16995b57b Reduce "docker pull" requests to dockerhub
new 5aa878721 Reduce "docker pull" requests to dockerhub
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 (16995b57b)
\
N -- N -- N refs/changes/77/37377/2 (5aa878721)
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/77/37377/1
in repository toolchain/jenkins-scripts.
discards 98f9b64e9 Reduce "docker pull" requests to dockerhub
new 942c4fd0d Reduce "docker pull" requests to dockerhub
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 (98f9b64e9)
\
N -- N -- N refs/changes/77/37377/1 (942c4fd0d)
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/77/34177/1
in repository toolchain/jenkins-scripts.
discards b6bfd2508 jenkins-helpers.sh: Update
adds d6054e034 jenkins-helpers.sh: Update
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 (b6bfd2508)
\
N -- N -- N refs/changes/77/34177/1 (d6054e034)
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/77/33977/1
in repository toolchain/jenkins-scripts.
discards e2245f201 tcwg_bmk-build.sh: Use LLD for LLVM configurations
adds 3d473238a tcwg_bmk-build.sh: Use LLD for LLVM configurations
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 (e2245f201)
\
N -- N -- N refs/changes/77/33977/1 (3d473238a)
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/77/32577/1
in repository toolchain/jenkins-scripts.
discards 4e9abe067 tcwg_bmk-build.sh: Use dynamic linking for code size tracking
adds 8841ca86f tcwg_bmk-build.sh: Use dynamic linking for code size tracking
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 (4e9abe067)
\
N -- N -- N refs/changes/77/32577/1 (8841ca86f)
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.