This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/23/45823/1
in repository toolchain/jenkins-scripts.
discards 1a1220b91 round-robin-notify.sh (update_interesting_commits): Fix thinko
discards 45ba72cc5 tcwg_bmk-build.sh: Rewrite all benchmarking history
adds 8d3910ecc tcwg_bmk-build.sh: Rewrite all benchmarking history
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 (1a1220b91)
\
N -- N -- N refs/changes/23/45823/1 (8d3910ecc)
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 | 553 --------------
round-robin-bisect.sh | 681 -----------------
round-robin-notify.sh | 1844 -----------------------------------------------
3 files changed, 3078 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/23/44623/3
in repository toolchain/jenkins-scripts.
discards d9889c1f7 round-robin-notify.sh: Cleanup handling of generate_* and pos [...]
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 (d9889c1f7)
\
N -- N -- N refs/changes/23/44623/3 (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 | 1522 -----------------------------------------------
3 files changed, 2341 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/23/44623/2
in repository toolchain/jenkins-scripts.
discards 8c5c3989a round-robin-notify.sh: Cleanup handling of generate_* and pos [...]
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 (8c5c3989a)
\
N -- N -- N refs/changes/23/44623/2 (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 | 1521 -----------------------------------------------
3 files changed, 2358 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/23/44623/1
in repository toolchain/jenkins-scripts.
discards 52a8a9fce round-robin-notify.sh: Cleanup handling of generate_* and pos [...]
discards a91f2cf04 round-robin-notify.sh: Restrict publishing of benchmark source
discards 879ff353d round-robin-notify.sh: Rework posting of jira comments
discards 5cbcc54cf round-robin-notify.sh: Create jira card for every interesting commit
discards 0fc893f2f round-robin.sh: Fix "ERROR: case (4) in check_regression" errors
adds f87dcca44 round-robin.sh: Fix "ERROR: case (4) in check_regression" errors
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 (52a8a9fce)
\
N -- N -- N refs/changes/23/44623/1 (f87dcca44)
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 | 1521 -----------------------------------------------
3 files changed, 2340 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/23/44523/3
in repository toolchain/jenkins-scripts.
discards bd197460c jenkins-helpers.sh (print_number_of_busy_executors): Improve
adds 97622211e jenkins-helpers.sh (print_number_of_busy_executors): Improve
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 (bd197460c)
\
N -- N -- N refs/changes/23/44523/3 (97622211e)
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/23/44523/2
in repository toolchain/jenkins-scripts.
discards 953d581d8 jenkins-helpers.sh: Fix shellcheck warning
new 65b683a12 jenkins-helpers.sh: Fix shellcheck warning
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 (953d581d8)
\
N -- N -- N refs/changes/23/44523/2 (65b683a12)
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/23/44523/1
in repository toolchain/jenkins-scripts.
discards d88611de4 jenkins-helpers.sh: Fix shellcheck warning
new ba117e503 jenkins-helpers.sh: Fix shellcheck warning
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 (d88611de4)
\
N -- N -- N refs/changes/23/44523/1 (ba117e503)
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/23/43823/2
in repository toolchain/jenkins-scripts.
discards 0879ad832 round-robin.sh (build_abe): Store ABE log files if ABE failed
adds d0ff7d8c5 round-robin.sh (build_abe): Store ABE log files if ABE failed
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 (0879ad832)
\
N -- N -- N refs/changes/23/43823/2 (d0ff7d8c5)
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/23/43823/1
in repository toolchain/jenkins-scripts.
discards e72a4c0fa round-robin.sh (build_abe): Store ABE log files if ABE failed
new 8550bf4af round-robin.sh (build_abe): Store ABE log files if ABE failed
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 (e72a4c0fa)
\
N -- N -- N refs/changes/23/43823/1 (8550bf4af)
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/23/43523/3
in repository toolchain/jenkins-scripts.
discards 509309a71 round-robin.sh: Disable external notification for all project
adds 44506195c round-robin.sh: Disable external notification for all project
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 (509309a71)
\
N -- N -- N refs/changes/23/43523/3 (44506195c)
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.