This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/13/45713/1
in repository toolchain/jenkins-scripts.
discards 8314a3fe6 generate-cimonitor-dashboard.py: Improve automatic diagnostic [...]
new 53e1cdd9c generate-cimonitor-dashboard.py: Improve automatic diagnostic [...]
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 (8314a3fe6)
\
N -- N -- N refs/changes/13/45713/1 (53e1cdd9c)
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/13/45613/2
in repository toolchain/jenkins-scripts.
discards ec386d638 start-container-docker.sh: Fix releasing of board lock file b [...]
adds 519d70762 start-container-docker.sh: Fix releasing of board lock file b [...]
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 (ec386d638)
\
N -- N -- N refs/changes/13/45613/2 (519d70762)
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/13/45613/1
in repository toolchain/jenkins-scripts.
discards f8fa2e6b9 start-container-docker.sh: Fix releasing of board lock file b [...]
new 385472908 start-container-docker.sh: Fix releasing of board lock file b [...]
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 (f8fa2e6b9)
\
N -- N -- N refs/changes/13/45613/1 (385472908)
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/13/45513/1
in repository toolchain/jenkins-scripts.
discards 68e7a8255 round-robin-notify.sh (print_mail_recipients): Rework
discards f665b453e round-robin-bisect.sh: Remove unneeded override
discards a0f52b969 round-robin-bisect.sh: Improve trigger for subsequent builds
adds 97d17c9ea round-robin-bisect.sh: Improve trigger for subsequent builds
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 (68e7a8255)
\
N -- N -- N refs/changes/13/45513/1 (97d17c9ea)
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 | 413 ------------
round-robin-bisect.sh | 655 -------------------
round-robin-notify.sh | 1588 -----------------------------------------------
3 files changed, 2656 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/13/45413/1
in repository toolchain/jenkins-scripts.
discards c57fc2638 Reland "tcwg-update-llvmbot-containers.sh: Add silent flang d [...]
adds bce7aba31 Reland "tcwg-update-llvmbot-containers.sh: Add silent flang d [...]
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 (c57fc2638)
\
N -- N -- N refs/changes/13/45413/1 (bce7aba31)
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/13/45113/2
in repository toolchain/jenkins-scripts.
discards 234058075 tcwg_bmk-build.sh: Fix bmk bisects.
adds 26b15aa9d tcwg_bmk-build.sh: Fix bmk bisects.
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 (234058075)
\
N -- N -- N refs/changes/13/45113/2 (26b15aa9d)
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/13/45113/1
in repository toolchain/jenkins-scripts.
discards c251299e9 tcwg_bmk-build.sh: Fix bmk bisects.
new 6e136f118 tcwg_bmk-build.sh: Fix bmk bisects.
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 (c251299e9)
\
N -- N -- N refs/changes/13/45113/1 (6e136f118)
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/13/44713/1
in repository toolchain/jenkins-scripts.
discards f0c6b92e2 pw-helpers.sh (pw_bundle_has_patch_p): Optimize to avoid hour [...]
adds 15ed330d2 pw-helpers.sh (pw_bundle_has_patch_p): Optimize to avoid hour [...]
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 (f0c6b92e2)
\
N -- N -- N refs/changes/13/44713/1 (15ed330d2)
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/13/44613/4
in repository toolchain/jenkins-scripts.
discards 7a32fb9fd round-robin-notify.sh: Restrict publishing of benchmark source
discards cafd97996 round-robin-notify.sh: Rework posting of jira comments
discards 1fcd1f776 round-robin.sh (build_abe): handle "transient" build failures
adds 4a0374c2d round-robin.sh (build_abe): handle "transient" build failures
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 (7a32fb9fd)
\
N -- N -- N refs/changes/13/44613/4 (4a0374c2d)
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 | 166 -----
round-robin-bisect.sh | 653 --------------------
round-robin-notify.sh | 1533 -----------------------------------------------
3 files changed, 2352 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/13/44613/3
in repository toolchain/jenkins-scripts.
discards 2dcfa7f24 round-robin-notify.sh: Restrict publishing of benchmark source
discards 4cf5bee73 round-robin-notify.sh: Rework posting of jira comments
discards ae0777e8d Revert "generate-cimonitor-dashboard.py: Fix file descriptors leak"
adds 802ebec98 Revert "generate-cimonitor-dashboard.py: Fix file descriptors leak"
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 (2dcfa7f24)
\
N -- N -- N refs/changes/13/44613/3 (802ebec98)
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 | 184 ------
round-robin-bisect.sh | 653 --------------------
round-robin-notify.sh | 1532 -----------------------------------------------
3 files changed, 2369 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.