This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/00/41700/1
in repository toolchain/jenkins-scripts.
discards b63c8f575 tcwg-update-llvmbot-containers.sh: Move 3 SVE bots to silent
new fbd9e068b tcwg-update-llvmbot-containers.sh: Move 3 SVE bots to silent
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 (b63c8f575)
\
N -- N -- N refs/changes/00/41700/1 (fbd9e068b)
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/00/39700/1
in repository toolchain/jenkins-scripts.
discards 52b65a7cc round-robin.sh: Add handling of COMMIT_* variables
adds 5ab52ea73 round-robin.sh: Add handling of COMMIT_* variables
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 (52b65a7cc)
\
N -- N -- N refs/changes/00/39700/1 (5ab52ea73)
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/00/37600/2
in repository toolchain/jenkins-scripts.
discards f7e8218a7 tcwg_kernel-build.sh: Use GNU Binutils for LLVM builds
adds 553b0e44b tcwg_kernel-build.sh: Use GNU Binutils for LLVM builds
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 (f7e8218a7)
\
N -- N -- N refs/changes/00/37600/2 (553b0e44b)
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/00/37600/1
in repository toolchain/jenkins-scripts.
discards 30d3c9618 tcwg_kernel-build.sh: Use GNU Binutils for LLVM builds
new 2b25cede7 tcwg_kernel-build.sh: Use GNU Binutils for LLVM builds
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 (30d3c9618)
\
N -- N -- N refs/changes/00/37600/1 (2b25cede7)
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/00/37000/2
in repository toolchain/jenkins-scripts.
discards 2c04efcb5 tcwg-generate-source-cache.sh: Remove support for llvm-reference
adds ca3886986 tcwg-generate-source-cache.sh: Remove support for llvm-reference
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 (2c04efcb5)
\
N -- N -- N refs/changes/00/37000/2 (ca3886986)
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/00/37000/1
in repository toolchain/jenkins-scripts.
discards 44984fd57 tcwg-generate-source-cache.sh: Remove support for llvm-reference
adds 0cc5f36c0 tcwg-generate-source-cache.sh: Remove support for llvm-reference
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 (44984fd57)
\
N -- N -- N refs/changes/00/37000/1 (0cc5f36c0)
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/00/35800/2
in repository toolchain/jenkins-scripts.
discards 582ec292a tcwg_gnu-build.sh: Use results comparison scripts from gcc-co [...]
adds 11ca90f66 tcwg_gnu-build.sh: Use results comparison scripts from gcc-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 (582ec292a)
\
N -- N -- N refs/changes/00/35800/2 (11ca90f66)
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/00/35800/1
in repository toolchain/jenkins-scripts.
discards 7d8629e83 tcwg_gnu-build.sh: Use results comparison scripts from gcc-co [...]
new bbd90c940 tcwg_gnu-build.sh: Use results comparison scripts from gcc-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 (7d8629e83)
\
N -- N -- N refs/changes/00/35800/1 (bbd90c940)
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/00/35200/1
in repository toolchain/jenkins-scripts.
discards e83c1921a jenkins-helpers.sh: Log run_step_init start and stop steps
adds f334446ad jenkins-helpers.sh: Log run_step_init start and stop steps
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 (e83c1921a)
\
N -- N -- N refs/changes/00/35200/1 (f334446ad)
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/00/31400/3
in repository toolchain/jenkins-scripts.
discards 284d53821 jenkins-helpers.sh: print_arch_for_label() Add support for tc [...]
adds 3b0636968 jenkins-helpers.sh: print_arch_for_label() Add support for tc [...]
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 (284d53821)
\
N -- N -- N refs/changes/00/31400/3 (3b0636968)
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.