This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/21/46421/3
in repository toolchain/jenkins-scripts.
discards 164931502 round-robin-baseline.sh,round-robin.sh: Move base-artifacts f [...]
new 29b6153aa round-robin-baseline.sh,round-robin.sh: Move base-artifacts f [...]
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 (164931502)
\
N -- N -- N refs/changes/21/46421/3 (29b6153aa)
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/21/46421/2
in repository toolchain/jenkins-scripts.
discards 9ee4ecb26 round-robin-baseline.sh,round-robin.sh: Move base-artifacts f [...]
new f345afb14 round-robin-baseline.sh,round-robin.sh: Move base-artifacts f [...]
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 (9ee4ecb26)
\
N -- N -- N refs/changes/21/46421/2 (f345afb14)
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/21/46421/1
in repository toolchain/jenkins-scripts.
discards 8ad8d3d73 round-robin-baseline.sh,round-robin.sh: Move base-artifacts f [...]
adds 90648d8ff round-robin-baseline.sh,round-robin.sh: Move base-artifacts f [...]
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 (8ad8d3d73)
\
N -- N -- N refs/changes/21/46421/1 (90648d8ff)
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/21/46321/2
in repository toolchain/jenkins-scripts.
discards fbc528be2 round-robin-notify.sh (release_testresults_files): Handle tes [...]
discards 2e82cfc13 round-robin.sh: ignore shellcheck
adds 19220fd8c round-robin.sh: ignore shellcheck
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 (fbc528be2)
\
N -- N -- N refs/changes/21/46321/2 (19220fd8c)
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-baseline.sh | 567 ------------
round-robin-bisect.sh | 681 --------------
round-robin-notify.sh | 2279 -----------------------------------------------
3 files changed, 3527 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.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/21/46321/1
in repository toolchain/jenkins-scripts.
discards 84e35a833 round-robin-notify.sh (release_testresults_files): Handle tes [...]
discards 0a5ec206f round-robin.sh (build_abe): Fix use of gnu_data for LAST_UPDATED
adds 4e4c1c89d round-robin.sh (build_abe): Fix use of gnu_data for LAST_UPDATED
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 (84e35a833)
\
N -- N -- N refs/changes/21/46321/1 (4e4c1c89d)
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-baseline.sh | 567 ------------
round-robin-bisect.sh | 681 --------------
round-robin-notify.sh | 2279 -----------------------------------------------
3 files changed, 3527 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.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/21/46221/3
in repository toolchain/jenkins-scripts.
discards 377049a98 tcwg-update-lnt-results.sh: Allow arguments to be all-projects
adds 77611b381 tcwg-update-lnt-results.sh: Allow arguments to be all-projects
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 (377049a98)
\
N -- N -- N refs/changes/21/46221/3 (77611b381)
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/21/46221/2
in repository toolchain/jenkins-scripts.
discards a53fbe803 tcwg-update-lnt-results.sh: Allow arguments to be all-projects
adds b9a3d5bb1 tcwg-update-lnt-results.sh: Allow arguments to be all-projects
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 (a53fbe803)
\
N -- N -- N refs/changes/21/46221/2 (b9a3d5bb1)
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/21/46221/1
in repository toolchain/jenkins-scripts.
discards 3fca62890 tcwg-update-lnt-results.sh: Allow arguments to be all-projects
adds f927a477b tcwg-update-lnt-results.sh: Allow arguments to be all-projects
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 (3fca62890)
\
N -- N -- N refs/changes/21/46221/1 (f927a477b)
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/21/46021/2
in repository toolchain/jenkins-scripts.
discards 3e03bdf37 tcwg-update-llvmbot-containers.sh: Move lldb Arm back to Focal
adds 343153594 tcwg-update-llvmbot-containers.sh: Move lldb Arm back to Focal
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 (3e03bdf37)
\
N -- N -- N refs/changes/21/46021/2 (343153594)
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/21/46021/1
in repository toolchain/jenkins-scripts.
discards 38c197774 tcwg-update-llvmbot-containers.sh: Move lldb Arm back to Focal
adds 849f88f68 tcwg-update-llvmbot-containers.sh: Move lldb Arm back to Focal
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 (38c197774)
\
N -- N -- N refs/changes/21/46021/1 (849f88f68)
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.