This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/24/44624/3
in repository toolchain/jenkins-scripts.
discards b3b7e25bb round-robin-notify.sh: Remove support for testing custom revisions
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 (b3b7e25bb)
\
N -- N -- N refs/changes/24/44624/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 | 1458 -----------------------------------------------
3 files changed, 2277 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/24/44624/2
in repository toolchain/jenkins-scripts.
discards 948138723 round-robin-notify.sh: Remove support for testing custom revisions
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 (948138723)
\
N -- N -- N refs/changes/24/44624/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 | 1457 -----------------------------------------------
3 files changed, 2294 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/24/44624/1
in repository toolchain/jenkins-scripts.
discards b38fc233b round-robin-notify.sh: Remove support for testing custom revisions
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 (b38fc233b)
\
N -- N -- N refs/changes/24/44624/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 | 1457 -----------------------------------------------
3 files changed, 2276 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/24/43224/4
in repository toolchain/jenkins-scripts.
discards e8bde0205 tcwg_bmk-build.sh: Build LLVM for ARMv8 host
adds 4ebce6a24 tcwg_bmk-build.sh: Build LLVM for ARMv8 host
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 (e8bde0205)
\
N -- N -- N refs/changes/24/43224/4 (4ebce6a24)
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/24/43224/3
in repository toolchain/jenkins-scripts.
discards 20cbb98b0 tcwg_bmk-build.sh: Build LLVM for ARMv8 host
adds 701438994 tcwg_bmk-build.sh: Build LLVM for ARMv8 host
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 (20cbb98b0)
\
N -- N -- N refs/changes/24/43224/3 (701438994)
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/24/43224/2
in repository toolchain/jenkins-scripts.
discards d639df3fd tcwg_bmk-build.sh: Build LLVM for ARMv8 host
adds 4401ee873 tcwg_bmk-build.sh: Build LLVM for ARMv8 host
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 (d639df3fd)
\
N -- N -- N refs/changes/24/43224/2 (4401ee873)
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/24/43224/1
in repository toolchain/jenkins-scripts.
discards 5cb863319 tcwg_bmk-build.sh: Build LLVM for ARMv8 host
adds 0b6b1e155 tcwg_bmk-build.sh: Build LLVM for ARMv8 host
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 (5cb863319)
\
N -- N -- N refs/changes/24/43224/1 (0b6b1e155)
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/24/42624/4
in repository toolchain/jenkins-scripts.
discards 16e78d419 wrappers/shadow-cc.sh: handle quoted filenames in rsp files
adds eb49dbd27 wrappers/shadow-cc.sh: handle quoted filenames in rsp files
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 (16e78d419)
\
N -- N -- N refs/changes/24/42624/4 (eb49dbd27)
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/24/42624/3
in repository toolchain/jenkins-scripts.
discards 9288e3054 wrappers/shadow-cc.sh: handle quoted filenames in rsp files
new 394dba9b5 wrappers/shadow-cc.sh: handle quoted filenames in rsp files
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 (9288e3054)
\
N -- N -- N refs/changes/24/42624/3 (394dba9b5)
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/24/42624/2
in repository toolchain/jenkins-scripts.
discards f01f7d86c wrappers/shadow-cc.sh: handle quoted filenames in rsp files
new 35de5da38 wrappers/shadow-cc.sh: handle quoted filenames in rsp files
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 (f01f7d86c)
\
N -- N -- N refs/changes/24/42624/2 (35de5da38)
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.