This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/cache-automerge/4e/1cd330ff60bfd95fece6d207fdc6e200996ca2
in repository toolchain/jenkins-scripts.
discards 4b2df5778 Auto-merge of 4e1cd330ff60bfd95fece6d207fdc6e200996ca2
new 3cd3d631b Auto-merge of 4e1cd330ff60bfd95fece6d207fdc6e200996ca2
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 (4b2df5778)
\
N -- N -- N refs/cache-automerge/4e/1cd330ff60bfd95fece6d207fdc6e200 [...]
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/cache-automerge/4c/939ef8a958bc45af89a493904cf30c5f2d81ee
in repository toolchain/jenkins-scripts.
discards 7977447b5 Auto-merge of 4c939ef8a958bc45af89a493904cf30c5f2d81ee
new 2a31f36c7 Auto-merge of 4c939ef8a958bc45af89a493904cf30c5f2d81ee
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 (7977447b5)
\
N -- N -- N refs/cache-automerge/4c/939ef8a958bc45af89a493904cf30c5f [...]
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/cache-automerge/0a/aeac20162756b12dfce5349ed61ee063410cb3
in repository toolchain/jenkins-scripts.
discards 55c5660ef Auto-merge of de85375bbac19758d5dbbbecb88cc79230fc543d
new cc6df9413 Auto-merge of de85375bbac19758d5dbbbecb88cc79230fc543d
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 (55c5660ef)
\
N -- N -- N refs/cache-automerge/0a/aeac20162756b12dfce5349ed61ee063 [...]
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 branch tested
in repository toolchain/jenkins-scripts.
discards 49dc24809 round-robin-notify.sh: Replace "progression" with "improvement"
discards bc3441401 Revert "tcwg-update-llvmbot-containers: Move Arm lldb bot to silent"
adds 8437865af Revert "tcwg-update-llvmbot-containers: Move Arm lldb bot 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
branch 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 (49dc24809)
\
N -- N -- N refs/heads/tested (8437865af)
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 | 650 -------------
round-robin-bisect.sh | 735 --------------
round-robin-notify.sh | 2429 -----------------------------------------------
3 files changed, 3814 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 branch tcwg_gnu
in repository toolchain/jenkins-scripts.
discards 0da0e554b tcwg_gnu-build.sh: Update after merge.
adds 10c09ebd4 tcwg_gnu-build.sh: Update after merge.
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch 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 (0da0e554b)
\
N -- N -- N refs/heads/tcwg_gnu (10c09ebd4)
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 branch tcwg_bmk
in repository toolchain/jenkins-scripts.
discards 5a0e2ea9b Merge branch 'master' into tcwg_bmk
adds a2ab659fb Merge branch 'master' into tcwg_bmk
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch 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 (5a0e2ea9b)
\
N -- N -- N refs/heads/tcwg_bmk (a2ab659fb)
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 branch rr-many
in repository toolchain/jenkins-scripts.
discards f60d65446 [rr-many 6/N] Improve update_baseline
new 3a794b979 [rr-many 6/N] Improve 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
branch 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 (f60d65446)
\
N -- N -- N refs/heads/rr-many (3a794b979)
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 branch precommit
in repository toolchain/jenkins-scripts.
discards 009504d7f start-container-docker.sh: Add "--task precommit"
new 13cede042 start-container-docker.sh: Add "--task precommit"
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch 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 (009504d7f)
\
N -- N -- N refs/heads/precommit (13cede042)
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 branch omair/release/19.0.0
in repository toolchain/jenkins-scripts.
discards bc3441401 Revert "tcwg-update-llvmbot-containers: Move Arm lldb bot to silent"
adds 8437865af Revert "tcwg-update-llvmbot-containers: Move Arm lldb bot 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
branch 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 (bc3441401)
\
N -- N -- N refs/heads/omair/release/19.0.0 (8437865af)
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 branch omair/release/17.0.0
in repository toolchain/jenkins-scripts.
discards 71972350d Disable flang + mlir for openmp build
new 21986589c Disable flang + mlir for openmp build
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch 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 (71972350d)
\
N -- N -- N refs/heads/omair/release/17.0.0 (21986589c)
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.