This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/67/34467/2
in repository toolchain/jenkins-scripts.
discards 73c89ab41 Add annotations to round-robin's "results" file
adds 4a9264364 Add annotations to round-robin's "results" file
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 (73c89ab41)
\
N -- N -- N refs/changes/67/34467/2 (4a9264364)
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/67/34467/1
in repository toolchain/jenkins-scripts.
discards 470ffc717 Add annotations to round-robin's "results" file
new 05908c75a Add annotations to round-robin's "results" file
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 (470ffc717)
\
N -- N -- N refs/changes/67/34467/1 (05908c75a)
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/67/32467/1
in repository toolchain/jenkins-scripts.
discards e84211d32 tcwg-benchmark-results.sh: Produce detailed "full" comparison
adds f52ec2bba tcwg-benchmark-results.sh: Produce detailed "full" comparison
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 (e84211d32)
\
N -- N -- N refs/changes/67/32467/1 (f52ec2bba)
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/67/31667/3
in repository toolchain/jenkins-scripts.
discards 91aa3917a tcwg_bmk-build.sh: Enable speed benchmarking
adds baa3be534 tcwg_bmk-build.sh: Enable speed benchmarking
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 (91aa3917a)
\
N -- N -- N refs/changes/67/31667/3 (baa3be534)
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/67/31667/2
in repository toolchain/jenkins-scripts.
discards fcff13639 tcwg_bmk-build.sh: Enable speed benchmarking
new 77844c9ae tcwg_bmk-build.sh: Enable speed benchmarking
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 (fcff13639)
\
N -- N -- N refs/changes/67/31667/2 (77844c9ae)
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/67/31667/1
in repository toolchain/jenkins-scripts.
discards 4e63ad25c tcwg_bmk-build.sh: Enable speed benchmarking
new 5cb60ea98 tcwg_bmk-build.sh: Enable speed benchmarking
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 (4e63ad25c)
\
N -- N -- N refs/changes/67/31667/1 (5cb60ea98)
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/67/30767/2
in repository toolchain/jenkins-scripts.
discards 04a47e724 tcwg_kernel-bisect.sh: Fix shell expansion
discards 7404092ad tcwg-benchmark.sh: Add support for clean_older_than
adds 31d3f7ccf tcwg-benchmark.sh: Add support for clean_older_than
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 (04a47e724)
\
N -- N -- N refs/changes/67/30767/2 (31d3f7ccf)
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:
tcwg_kernel-bisect.sh | 480 --------------------------------------------------
1 file changed, 480 deletions(-)
delete mode 100755 tcwg_kernel-bisect.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/67/30767/1
in repository toolchain/jenkins-scripts.
discards 39391cf68 tcwg_kernel-bisect.sh: Fix shell expansion
discards 82cbd12c5 tcwg_kernel-bisect.sh: Always add $first_bad to interesting-c [...]
discards 7b44d0602 tcwg-update-snapshots_ref.sh: Use tcwg-tk1_32-build label ins [...]
adds 2d800210c tcwg-update-snapshots_ref.sh: Use tcwg-tk1_32-build label ins [...]
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 (39391cf68)
\
N -- N -- N refs/changes/67/30767/1 (2d800210c)
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:
tcwg_kernel-bisect.sh | 480 --------------------------------------------------
1 file changed, 480 deletions(-)
delete mode 100755 tcwg_kernel-bisect.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/67/30667/4
in repository toolchain/jenkins-scripts.
discards e53831da2 tcwg_kernel-bisect.sh: Add support for regression cache
discards 51e051a16 print_nodes_in_labels: Handle empty labels
adds 11b21401e print_nodes_in_labels: Handle empty labels
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 (e53831da2)
\
N -- N -- N refs/changes/67/30667/4 (11b21401e)
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:
tcwg_kernel-bisect.sh | 471 --------------------------------------------------
1 file changed, 471 deletions(-)
delete mode 100755 tcwg_kernel-bisect.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/67/30667/3
in repository toolchain/jenkins-scripts.
discards d39b501a6 tcwg_kernel-bisect.sh: Add support for regression cache
discards d7f15cdb0 tcwg_kernel-bisect.sh: Match GCC ICEs in the logs
discards 04ed7f8fe tcwg_kernel-bisect.sh: Use llvm@ and tcwg-gcc@ groups in emai [...]
discards f91cadd37 tcwg-cleanup-stale-containers.sh: Make output easier to understand.
adds 7d0f64976 tcwg-cleanup-stale-containers.sh: Make output easier to understand.
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 (d39b501a6)
\
N -- N -- N refs/changes/67/30667/3 (7d0f64976)
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:
tcwg_kernel-bisect.sh | 471 --------------------------------------------------
1 file changed, 471 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.