This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/21/32421/1
in repository toolchain/jenkins-scripts.
discards c5f12aeb2 tcwg-update-llvmbot-containers.sh: Don't run bots on thx1
adds 07ad769f8 tcwg-update-llvmbot-containers.sh: Don't run bots on thx1
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 (c5f12aeb2)
\
N -- N -- N refs/changes/21/32421/1 (07ad769f8)
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/31221/2
in repository toolchain/jenkins-scripts.
discards 00a144341 jenkins-helpers.sh: Add close_baseline_repo helper
adds fb77764f3 jenkins-helpers.sh: Add close_baseline_repo helper
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 (00a144341)
\
N -- N -- N refs/changes/21/31221/2 (fb77764f3)
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/31221/1
in repository toolchain/jenkins-scripts.
discards 77869b6ac jenkins-helpers.sh: Add close_baseline_repo helper
adds da296b33b jenkins-helpers.sh: Add close_baseline_repo helper
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 (77869b6ac)
\
N -- N -- N refs/changes/21/31221/1 (da296b33b)
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/30721/1
in repository toolchain/jenkins-scripts.
discards 51e051a16 print_nodes_in_labels: Handle empty labels
adds 11b21401e print_nodes_in_labels: Handle empty labels
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 (51e051a16)
\
N -- N -- N refs/changes/21/30721/1 (11b21401e)
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/30221/3
in repository toolchain/jenkins-scripts.
discards 99300555a jenkins-helpers.sh: Workaround DNS issue
adds 06af2d36b jenkins-helpers.sh: Workaround DNS issue
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 (99300555a)
\
N -- N -- N refs/changes/21/30221/3 (06af2d36b)
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/30221/2
in repository toolchain/jenkins-scripts.
discards c8f9e41ed jenkins-helpers.sh: Workaround DNS issue
new aae74eaf8 jenkins-helpers.sh: Workaround DNS issue
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 (c8f9e41ed)
\
N -- N -- N refs/changes/21/30221/2 (aae74eaf8)
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/30221/1
in repository toolchain/jenkins-scripts.
discards f7020a362 jenkins-helpers.sh: Workaround DNS issue
new 91f8b27ee jenkins-helpers.sh: Workaround DNS issue
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 (f7020a362)
\
N -- N -- N refs/changes/21/30221/1 (91f8b27ee)
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/30121/1
in repository toolchain/jenkins-scripts.
discards 8550a2d0a tcwg_kernel-bisect: Fix typo.
discards 33a2a22f9 tcwg_kernel-bisect: Fix bisect script to use rr[top_artifacts [...]
discards 8bd6a240f round-robin: Fix reset_baseline with previous patch
adds 23ff3f6b2 round-robin: Fix reset_baseline with previous patch
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 (8550a2d0a)
\
N -- N -- N refs/changes/21/30121/1 (23ff3f6b2)
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:
tcwg_kernel-bisect.sh | 362 --------------------------------------------------
1 file changed, 362 deletions(-)
delete mode 100755 tcwg_kernel-bisect.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/29621/2
in repository toolchain/jenkins-scripts.
discards f238c3d99 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
adds de5d2bdf3 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
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 (f238c3d99)
\
N -- N -- N refs/changes/21/29621/2 (de5d2bdf3)
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/29621/1
in repository toolchain/jenkins-scripts.
discards 38a883d64 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
adds 75c9233c3 tcwg_kernel-build.sh: Make sure manifest declares variables i [...]
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 (38a883d64)
\
N -- N -- N refs/changes/21/29621/1 (75c9233c3)
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.