This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/14/43314/2
in repository toolchain/jenkins-scripts.
discards 8f1f1eae3 tcwg_aosp-build.sh: Use baseline branch under linaro-local/ci/*
adds 07edb71cb tcwg_aosp-build.sh: Use baseline branch under linaro-local/ci/*
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 (8f1f1eae3)
\
N -- N -- N refs/changes/14/43314/2 (07edb71cb)
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/14/43314/1
in repository toolchain/jenkins-scripts.
discards d3c45780c tcwg_aosp-build.sh: Use baseline branch under linaro-local/ci/*
adds 16af28db9 tcwg_aosp-build.sh: Use baseline branch under linaro-local/ci/*
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 (d3c45780c)
\
N -- N -- N refs/changes/14/43314/1 (16af28db9)
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/14/42114/1
in repository toolchain/jenkins-scripts.
discards 1f768df10 dashboard-generate-squad.sh: skip header
adds bba0e8fae dashboard-generate-squad.sh: skip header
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 (1f768df10)
\
N -- N -- N refs/changes/14/42114/1 (bba0e8fae)
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/14/39914/1
in repository toolchain/jenkins-scripts.
discards a88254439 tcwg-start-container.sh: Send SIGTERM to gracefully shutdown [...]
adds ce6702fbb tcwg-start-container.sh: Send SIGTERM to gracefully shutdown [...]
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 (a88254439)
\
N -- N -- N refs/changes/14/39914/1 (ce6702fbb)
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/14/39314/1
in repository toolchain/jenkins-scripts.
discards f85b5a598 tcwg-update-llvmbot-containers.sh: Correct "normal" to "build [...]
adds c7b28f4e3 tcwg-update-llvmbot-containers.sh: Correct "normal" to "build [...]
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 (f85b5a598)
\
N -- N -- N refs/changes/14/39314/1 (c7b28f4e3)
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/14/38614/2
in repository toolchain/jenkins-scripts.
discards d13978e82 tcwg_kernel-build.sh: Speed up bisections of qemu regressions
adds c9cd8b7e0 tcwg_kernel-build.sh: Speed up bisections of qemu regressions
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 (d13978e82)
\
N -- N -- N refs/changes/14/38614/2 (c9cd8b7e0)
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/14/38614/1
in repository toolchain/jenkins-scripts.
discards 7ab60d2c3 tcwg_kernel-build.sh: Speed up bisections of qemu regressions
adds 6347b9815 tcwg_kernel-build.sh: Speed up bisections of qemu regressions
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 (7ab60d2c3)
\
N -- N -- N refs/changes/14/38614/1 (6347b9815)
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/14/36914/1
in repository toolchain/jenkins-scripts.
discards 7cb2be672 update-llvmbot-containers: Add flang-dylib/shlibs
adds 57fe3e463 update-llvmbot-containers: Add flang-dylib/shlibs
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 (7cb2be672)
\
N -- N -- N refs/changes/14/36914/1 (57fe3e463)
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/14/36114/5
in repository toolchain/jenkins-scripts.
discards 71dfb529f tcwg-benchmark-results.sh: Add support for --has_perf_logs option
adds 3edf82950 tcwg-benchmark-results.sh: Add support for --has_perf_logs option
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 (71dfb529f)
\
N -- N -- N refs/changes/14/36114/5 (3edf82950)
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/14/36114/4
in repository toolchain/jenkins-scripts.
discards ace9a2f53 tcwg-benchmark-results.sh: Add support for --has_perf_logs option
new 43db243b3 tcwg-benchmark-results.sh: Add support for --has_perf_logs option
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 (ace9a2f53)
\
N -- N -- N refs/changes/14/36114/4 (43db243b3)
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.