This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/01/35401/1
in repository toolchain/jenkins-scripts.
discards 45de43ea0 tcwg-update-llvmbot-containers.sh: Update bot names to match zorg
adds e039cce48 tcwg-update-llvmbot-containers.sh: Update bot names to match zorg
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 (45de43ea0)
\
N -- N -- N refs/changes/01/35401/1 (e039cce48)
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/01/35201/1
in repository toolchain/jenkins-scripts.
discards 765d89c21 jenkins-helpers.sh: Clarify HANDLING failure message
adds 624ea4a0b jenkins-helpers.sh: Clarify HANDLING failure message
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 (765d89c21)
\
N -- N -- N refs/changes/01/35201/1 (624ea4a0b)
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/01/32401/1
in repository toolchain/jenkins-scripts.
discards e5a9fa52d tcwg_bmk-build.sh: Use 10% tolerances for symbols
adds ceb789275 tcwg_bmk-build.sh: Use 10% tolerances for symbols
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 (e5a9fa52d)
\
N -- N -- N refs/changes/01/32401/1 (ceb789275)
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/01/31401/3
in repository toolchain/jenkins-scripts.
discards 7da4c37bf jenkins-helpers: print_arch_for_label: Sort labels for easier [...]
adds 42b3f9caa jenkins-helpers: print_arch_for_label: Sort labels for easier [...]
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 (7da4c37bf)
\
N -- N -- N refs/changes/01/31401/3 (42b3f9caa)
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/01/31401/2
in repository toolchain/jenkins-scripts.
discards 2b67ff0ae jenkins-helpers: print_arch_for_label: Sort labels for easier [...]
new 52c8aa0cd jenkins-helpers: print_arch_for_label: Sort labels for easier [...]
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 (2b67ff0ae)
\
N -- N -- N refs/changes/01/31401/2 (52c8aa0cd)
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/01/31401/1
in repository toolchain/jenkins-scripts.
discards 62dc90455 jenkins-helpers: print_arch_for_label: Sort labels for easier [...]
new e7a376d62 jenkins-helpers: print_arch_for_label: Sort labels for easier [...]
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 (62dc90455)
\
N -- N -- N refs/changes/01/31401/1 (e7a376d62)
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/01/30901/3
in repository toolchain/jenkins-scripts.
discards 47b5f3241 round-robin.sh: Refactor reset_baseline into update_baseline
adds 5599800c4 round-robin.sh: Refactor reset_baseline into update_baseline
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 (47b5f3241)
\
N -- N -- N refs/changes/01/30901/3 (5599800c4)
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/01/30901/2
in repository toolchain/jenkins-scripts.
discards e0af34e98 round-robin.sh: Refactor reset_baseline into update_baseline
adds 9fdb6c7b0 round-robin.sh: Refactor reset_baseline into update_baseline
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 (e0af34e98)
\
N -- N -- N refs/changes/01/30901/2 (9fdb6c7b0)
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/01/30901/1
in repository toolchain/jenkins-scripts.
discards 8db5ead92 round-robin.sh: Refactor reset_baseline into update_baseline
adds 6dc52abbc round-robin.sh: Refactor reset_baseline into update_baseline
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 (8db5ead92)
\
N -- N -- N refs/changes/01/30901/1 (6dc52abbc)
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/01/30401/2
in repository toolchain/jenkins-scripts.
discards f42643fad Trivial cleanups
adds 79307ecf4 Trivial cleanups
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 (f42643fad)
\
N -- N -- N refs/changes/01/30401/2 (79307ecf4)
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.