This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/22/45622/3
in repository toolchain/jenkins-scripts.
discards ab201d7df round-robin-notify.sh (print_commits): Improve handling of pr [...]
discards f9ca877da round-robin-baseline.sh (rewrite_single_revision): Fix corner-case
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 (ab201d7df)
\
N -- N -- N refs/changes/22/45622/3 (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:
round-robin-baseline.sh | 455 -------------
round-robin-bisect.sh | 655 -------------------
round-robin-notify.sh | 1628 -----------------------------------------------
3 files changed, 2738 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/22/45622/2
in repository toolchain/jenkins-scripts.
discards d85fe3969 round-robin-notify.sh (print_commits): Improve handling of pr [...]
discards f9ca877da round-robin-baseline.sh (rewrite_single_revision): Fix corner-case
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 (d85fe3969)
\
N -- N -- N refs/changes/22/45622/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:
round-robin-baseline.sh | 455 -------------
round-robin-bisect.sh | 655 -------------------
round-robin-notify.sh | 1628 -----------------------------------------------
3 files changed, 2738 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/22/45622/1
in repository toolchain/jenkins-scripts.
discards 30084fbcb round-robin-notify.sh (print_commits): Improve handling of pr [...]
discards 5aed98ae0 round-robin.sh (reset_artifacts): Skip components that are ab [...]
new 78151ff84 round-robin.sh (reset_artifacts): Skip components that are ab [...]
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 (30084fbcb)
\
N -- N -- N refs/changes/22/45622/1 (78151ff84)
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:
round-robin-baseline.sh | 455 -------------
round-robin-bisect.sh | 655 -------------------
round-robin-notify.sh | 1628 -----------------------------------------------
3 files changed, 2738 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/22/44522/1
in repository toolchain/jenkins-scripts.
discards 32931b84f jenkins-helpers.sh (print_number_of_busy_executors): New function
adds febe0055a jenkins-helpers.sh (print_number_of_busy_executors): New function
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 (32931b84f)
\
N -- N -- N refs/changes/22/44522/1 (febe0055a)
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/22/43822/2
in repository toolchain/jenkins-scripts.
discards c0db99871 round-robin.sh (build_abe): Store sum files even if ABE faile [...]
adds 734777876 round-robin.sh (build_abe): Store sum files even if ABE faile [...]
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 (c0db99871)
\
N -- N -- N refs/changes/22/43822/2 (734777876)
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/22/43822/1
in repository toolchain/jenkins-scripts.
discards 5b3824bfc round-robin.sh (build_abe): Store sum files even if ABE faile [...]
adds 4ef0139da round-robin.sh (build_abe): Store sum files even if ABE faile [...]
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 (5b3824bfc)
\
N -- N -- N refs/changes/22/43822/1 (4ef0139da)
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/22/41922/2
in repository toolchain/jenkins-scripts.
discards 89448a2b3 tcwg_kernel-build.sh: Cleanup / simplify
adds eaf21843a tcwg_kernel-build.sh: Cleanup / simplify
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 (89448a2b3)
\
N -- N -- N refs/changes/22/41922/2 (eaf21843a)
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/22/41922/1
in repository toolchain/jenkins-scripts.
discards 705aac54c tcwg_kernel-build.sh: Cleanup / simplify
adds ffc524aeb tcwg_kernel-build.sh: Cleanup / simplify
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 (705aac54c)
\
N -- N -- N refs/changes/22/41922/1 (ffc524aeb)
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/22/41322/1
in repository toolchain/jenkins-scripts.
discards e0ad973d7 tcwg-benchmark.sh: Use ssh port specified in .ssh/config
adds 46638b3b5 tcwg-benchmark.sh: Use ssh port specified in .ssh/config
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 (e0ad973d7)
\
N -- N -- N refs/changes/22/41322/1 (46638b3b5)
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/22/39922/2
in repository toolchain/jenkins-scripts.
discards 34eccce6e start-container-docker.sh: Add workaround for armhf focal con [...]
adds f6852e4d0 start-container-docker.sh: Add workaround for armhf focal con [...]
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 (34eccce6e)
\
N -- N -- N refs/changes/22/39922/2 (f6852e4d0)
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.