This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/07/43507/1
in repository toolchain/jenkins-scripts.
discards dd27fbde7 wrappers/shadow-cc.sh: Fix ccache using AOSP compiler wrapper
adds cc8e2eb95 wrappers/shadow-cc.sh: Fix ccache using AOSP compiler wrapper
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 (dd27fbde7)
\
N -- N -- N refs/changes/07/43507/1 (cc8e2eb95)
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/07/42407/1
in repository toolchain/jenkins-scripts.
discards 39904eda6 tcwg-report-ci-status.sh: New script to dump a CI status
adds 66e1a13eb tcwg-report-ci-status.sh: New script to dump a CI status
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 (39904eda6)
\
N -- N -- N refs/changes/07/42407/1 (66e1a13eb)
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/07/42307/2
in repository toolchain/jenkins-scripts.
discards d9c85923f tcwg-llvmbot: Move aarch64-full-2stage to silent for fixed co [...]
adds 2b95c5737 tcwg-llvmbot: Move aarch64-full-2stage to silent for fixed co [...]
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 (d9c85923f)
\
N -- N -- N refs/changes/07/42307/2 (2b95c5737)
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/07/42307/1
in repository toolchain/jenkins-scripts.
discards ee40ecab7 tcwg-llvmbot: Move aarch64-full-2stage to silent for fixed co [...]
adds 912194789 tcwg-llvmbot: Move aarch64-full-2stage to silent for fixed co [...]
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 (ee40ecab7)
\
N -- N -- N refs/changes/07/42307/1 (912194789)
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/07/39307/3
in repository toolchain/jenkins-scripts.
discards d29d157e6 tcwg-benchmark.sh: Stop using $BUILD_NUMBER
adds 9add129e7 tcwg-benchmark.sh: Stop using $BUILD_NUMBER
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 (d29d157e6)
\
N -- N -- N refs/changes/07/39307/3 (9add129e7)
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/07/39307/2
in repository toolchain/jenkins-scripts.
discards d27a2e7e8 tcwg-benchmark.sh: Stop using $BUILD_NUMBER
adds e54c15c87 tcwg-benchmark.sh: Stop using $BUILD_NUMBER
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 (d27a2e7e8)
\
N -- N -- N refs/changes/07/39307/2 (e54c15c87)
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/07/39307/1
in repository toolchain/jenkins-scripts.
discards f28337f89 tcwg-benchmark.sh: Stop using $BUILD_NUMBER
adds 08743f371 tcwg-benchmark.sh: Stop using $BUILD_NUMBER
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 (f28337f89)
\
N -- N -- N refs/changes/07/39307/1 (08743f371)
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/07/37407/2
in repository toolchain/jenkins-scripts.
discards e3dff5bb4 round-robin-bisect.sh: Remove obsolete marker
discards 8b78dcbbb round-robin-bisect.sh: Generalize logic of handling "reset" commit
discards 499beadee round-robin-bisect.sh: Make handling of unsuccessful bisects [...]
discards 36aa35cac round-robin-bisect.sh: Make code to trigger follow-up builds [...]
discards d04c755cb round-robin-bisect.sh: Make logic of handling successful bise [...]
discards 8bdc7c170 round-robin-bisect.sh: Simplify filtering of interesting commits
discards a9ee3b7ff tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
adds e1b7cb695 tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
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 (e3dff5bb4)
\
N -- N -- N refs/changes/07/37407/2 (e1b7cb695)
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 | 719 --------------------------------------------------
1 file changed, 719 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/07/37407/1
in repository toolchain/jenkins-scripts.
discards 44f80bcd0 round-robin-bisect.sh: Remove obsolete marker
discards 9f50f518c round-robin-bisect.sh: Generalize logic of handling "reset" commit
discards fbdf19b02 round-robin-bisect.sh: Make handling of unsuccessful bisects [...]
discards 36aa35cac round-robin-bisect.sh: Make code to trigger follow-up builds [...]
discards d04c755cb round-robin-bisect.sh: Make logic of handling successful bise [...]
discards 8bdc7c170 round-robin-bisect.sh: Simplify filtering of interesting commits
discards a9ee3b7ff tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
adds e1b7cb695 tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
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 (44f80bcd0)
\
N -- N -- N refs/changes/07/37407/1 (e1b7cb695)
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 | 719 --------------------------------------------------
1 file changed, 719 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/07/32907/1
in repository toolchain/jenkins-scripts.
discards 2f77cdd3d update-llvmbot-containers.sh: Update after node rename in Jenkins
adds 258700d9f update-llvmbot-containers.sh: Update after node rename in Jenkins
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 (2f77cdd3d)
\
N -- N -- N refs/changes/07/32907/1 (258700d9f)
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.