This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/76/44276/2
in repository toolchain/jenkins-scripts.
discards faf8b00a7 round-robin-notify.sh: Add compatibility code to use older artifacts
discards b0b1d416a round-robin-notify.sh: Exits with a warning if revision of ba [...]
discards 1812cb222 round-robin-notify.sh: rewrite for readability
discards 1b564e14b Revert "tcwg-update-llvmbot-containers.sh: Experiment with ru [...]
adds 7f3edfe19 Revert "tcwg-update-llvmbot-containers.sh: Experiment with ru [...]
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 (faf8b00a7)
\
N -- N -- N refs/changes/76/44276/2 (7f3edfe19)
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 | 647 --------------------------
round-robin-notify.sh | 1226 -------------------------------------------------
2 files changed, 1873 deletions(-)
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/76/44276/1
in repository toolchain/jenkins-scripts.
discards 6390b59cd round-robin-notify.sh: Add compatibility code to use older artifacts
discards b0b1d416a round-robin-notify.sh: Exits with a warning if revision of ba [...]
discards 1812cb222 round-robin-notify.sh: rewrite for readability
discards 1b564e14b Revert "tcwg-update-llvmbot-containers.sh: Experiment with ru [...]
adds 7f3edfe19 Revert "tcwg-update-llvmbot-containers.sh: Experiment with ru [...]
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 (6390b59cd)
\
N -- N -- N refs/changes/76/44276/1 (7f3edfe19)
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 | 647 --------------------------
round-robin-notify.sh | 1228 -------------------------------------------------
2 files changed, 1875 deletions(-)
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/76/44176/1
in repository toolchain/jenkins-scripts.
discards cb5c57e2d shadow-cc.sh: relax check on rsp filenames
adds 3c4c7bd02 shadow-cc.sh: relax check on rsp filenames
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 (cb5c57e2d)
\
N -- N -- N refs/changes/76/44176/1 (3c4c7bd02)
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/76/43676/2
in repository toolchain/jenkins-scripts.
discards 9c6950372 tcwg_bmk-config.sh: Remove workaround for noisy SPEC2k6 benchmarks
adds 645d64cb5 tcwg_bmk-config.sh: Remove workaround for noisy SPEC2k6 benchmarks
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 (9c6950372)
\
N -- N -- N refs/changes/76/43676/2 (645d64cb5)
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/76/43676/1
in repository toolchain/jenkins-scripts.
discards f5e608a28 tcwg_bmk-config.sh: Remove workaround for noisy SPEC2k6 benchmarks
adds 6c58bc479 tcwg_bmk-config.sh: Remove workaround for noisy SPEC2k6 benchmarks
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 (f5e608a28)
\
N -- N -- N refs/changes/76/43676/1 (6c58bc479)
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/76/42776/3
in repository toolchain/jenkins-scripts.
discards f85283782 Apply llvm-vect-metric.diff patch to LLVM only for VECT configs.
adds d34afa0bb Apply llvm-vect-metric.diff patch to LLVM only for VECT configs.
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 (f85283782)
\
N -- N -- N refs/changes/76/42776/3 (d34afa0bb)
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/76/42776/2
in repository toolchain/jenkins-scripts.
discards d9a278cff Apply llvm-vect-metric.diff patch to LLVM only for VECT configs.
new 6c9d466b9 Apply llvm-vect-metric.diff patch to LLVM only for VECT configs.
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 (d9a278cff)
\
N -- N -- N refs/changes/76/42776/2 (6c9d466b9)
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/76/42776/1
in repository toolchain/jenkins-scripts.
discards 4101aa283 Apply llvm-vect-metric.diff patch to LLVM only for VECT configs.
new 42c1da4a4 Apply llvm-vect-metric.diff patch to LLVM only for VECT configs.
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 (4101aa283)
\
N -- N -- N refs/changes/76/42776/1 (42c1da4a4)
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/76/42376/2
in repository toolchain/jenkins-scripts.
discards d777d07ab round-robin.sh,tcwg_bmk-build.sh,tcwg_kernel-build.sh: Add op [...]
new 85c2754fd round-robin.sh,tcwg_bmk-build.sh,tcwg_kernel-build.sh: Add op [...]
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 (d777d07ab)
\
N -- N -- N refs/changes/76/42376/2 (85c2754fd)
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/76/42376/1
in repository toolchain/jenkins-scripts.
discards d2aa2b10b round-robin.sh: Build llvm with clang when asking for flang
new e3ddc3fc7 round-robin.sh: Build llvm with clang when asking for flang
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 (d2aa2b10b)
\
N -- N -- N refs/changes/76/42376/1 (e3ddc3fc7)
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.