This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/45/46945/1
in repository toolchain/jenkins-scripts.
discards 2d4cddb4d (WIP) jenkins-helpers.sh: print_changed_components can work i [...]
adds 3ae10a93f (WIP) jenkins-helpers.sh: print_changed_components can work 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 (2d4cddb4d)
\
N -- N -- N refs/changes/45/46945/1 (3ae10a93f)
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/45/46445/3
in repository toolchain/jenkins-scripts.
discards 0691cc506 lnt-utils.sh: Adjust git information
adds a0def03fa lnt-utils.sh: Adjust git information
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 (0691cc506)
\
N -- N -- N refs/changes/45/46445/3 (a0def03fa)
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/45/46445/2
in repository toolchain/jenkins-scripts.
discards 78fe1fd44 lnt-utils.sh: Adjust git information
adds 7b082494a lnt-utils.sh: Adjust git information
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 (78fe1fd44)
\
N -- N -- N refs/changes/45/46445/2 (7b082494a)
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/45/46445/1
in repository toolchain/jenkins-scripts.
discards 2b253633e lnt-utils.sh: Adjust git information
adds b62ecff31 lnt-utils.sh: Adjust git information
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 (2b253633e)
\
N -- N -- N refs/changes/45/46445/1 (b62ecff31)
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/45/46145/2
in repository toolchain/jenkins-scripts.
discards f80fe64b1 pw-trigger.sh: Wait for prerequisite bots to complete
adds a72c82dbb pw-trigger.sh: Wait for prerequisite bots to complete
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 (f80fe64b1)
\
N -- N -- N refs/changes/45/46145/2 (a72c82dbb)
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/45/46145/1
in repository toolchain/jenkins-scripts.
discards 5c11948d0 pw-trigger.sh: Wait for prerequisite bots to complete
adds 3dd3584d3 pw-trigger.sh: Wait for prerequisite bots to complete
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 (5c11948d0)
\
N -- N -- N refs/changes/45/46145/1 (3dd3584d3)
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/45/44545/1
in repository toolchain/jenkins-scripts.
discards b47ba7b6d tcwg-update-llvmbot-containers: Start silent graviton 02/03 o [...]
adds 0744758ae tcwg-update-llvmbot-containers: Start silent graviton 02/03 o [...]
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 (b47ba7b6d)
\
N -- N -- N refs/changes/45/44545/1 (0744758ae)
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/45/44445/2
in repository toolchain/jenkins-scripts.
discards 27c2211bf tcwg_gnu-build.sh: Decrease validate_failures.py verbosity to 2
adds b121e3acb tcwg_gnu-build.sh: Decrease validate_failures.py verbosity to 2
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 (27c2211bf)
\
N -- N -- N refs/changes/45/44445/2 (b121e3acb)
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/45/44445/1
in repository toolchain/jenkins-scripts.
discards 8db4920b4 tcwg_gnu-build.sh: Decrease validate_failures.py verbosity to 2
new c16787557 tcwg_gnu-build.sh: Decrease validate_failures.py verbosity to 2
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 (8db4920b4)
\
N -- N -- N refs/changes/45/44445/1 (c16787557)
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/45/43745/5
in repository toolchain/jenkins-scripts.
discards f30fbe254 round-robin.sh (build_abe): Re-run testsuites until convergence
adds a7128caab round-robin.sh (build_abe): Re-run testsuites until convergence
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 (f30fbe254)
\
N -- N -- N refs/changes/45/43745/5 (a7128caab)
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.