This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/30/42430/2
in repository toolchain/jenkins-scripts.
discards 946ca92fc tcwg-update-llvmbot-containers.sh: Add clang-armv8-quick worker
adds 8fa116724 tcwg-update-llvmbot-containers.sh: Add clang-armv8-quick worker
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 (946ca92fc)
\
N -- N -- N refs/changes/30/42430/2 (8fa116724)
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/30/42430/1
in repository toolchain/jenkins-scripts.
discards a20a03440 tcwg-update-llvmbot-containers.sh: Add clang-armv8-quick worker
adds 5ed46d1d8 tcwg-update-llvmbot-containers.sh: Add clang-armv8-quick worker
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 (a20a03440)
\
N -- N -- N refs/changes/30/42430/1 (5ed46d1d8)
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/30/42130/5
in repository toolchain/jenkins-scripts.
discards 7064b75df tcwg_bmk-build.sh: Generate comparison csv files even for fir [...]
adds 119fcb2b8 tcwg_bmk-build.sh: Generate comparison csv files even for fir [...]
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 (7064b75df)
\
N -- N -- N refs/changes/30/42130/5 (119fcb2b8)
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/30/42130/4
in repository toolchain/jenkins-scripts.
discards fc840a69d tcwg_bmk-build.sh: Generate comparison csv files even for fir [...]
adds 1c5a4a41a tcwg_bmk-build.sh: Generate comparison csv files even for fir [...]
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 (fc840a69d)
\
N -- N -- N refs/changes/30/42130/4 (1c5a4a41a)
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/30/42130/3
in repository toolchain/jenkins-scripts.
discards 72f8c2d71 tcwg_bmk-build.sh: Generate comparison csv files even for fir [...]
adds 7064557a8 tcwg_bmk-build.sh: Generate comparison csv files even for fir [...]
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 (72f8c2d71)
\
N -- N -- N refs/changes/30/42130/3 (7064557a8)
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/30/42130/2
in repository toolchain/jenkins-scripts.
discards bf959ed26 tcwg_bmk-build.sh: copy bare results of the run to artifacts
adds 9feb48894 tcwg_bmk-build.sh: copy bare results of the run to artifacts
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 (bf959ed26)
\
N -- N -- N refs/changes/30/42130/2 (9feb48894)
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/30/42130/1
in repository toolchain/jenkins-scripts.
discards 6c82ace34 tcwg_bmk-build.sh: copy bare results of the run to artifacts
new f750ee1b4 tcwg_bmk-build.sh: copy bare results of the run to artifacts
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 (6c82ace34)
\
N -- N -- N refs/changes/30/42130/1 (f750ee1b4)
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/30/42030/2
in repository toolchain/jenkins-scripts.
discards d259de238 round-robin.sh: Simplfy again dashboard generation
adds 4eeb0601f round-robin.sh: Simplfy again dashboard generation
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 (d259de238)
\
N -- N -- N refs/changes/30/42030/2 (4eeb0601f)
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/30/42030/1
in repository toolchain/jenkins-scripts.
discards c99513790 round-robin.sh: Simplfy again dashboard generation
new 9efe33b64 round-robin.sh: Simplfy again dashboard generation
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 (c99513790)
\
N -- N -- N refs/changes/30/42030/1 (9efe33b64)
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/30/41830/1
in repository toolchain/jenkins-scripts.
discards 836b21266 round-robin.sh: Fix "git rev-parse" of short histories
adds d90fd211c round-robin.sh: Fix "git rev-parse" of short histories
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 (836b21266)
\
N -- N -- N refs/changes/30/41830/1 (d90fd211c)
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.