This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/33063/1
in repository toolchain/jenkins-scripts.
discards 5fe7960d5 tcwg_bmk-build.sh: Add more comments
adds b10e0efc4 tcwg_bmk-build.sh: Add more comments
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 (5fe7960d5)
\
N -- N -- N refs/changes/63/33063/1 (b10e0efc4)
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/63/30863/1
in repository toolchain/jenkins-scripts.
discards 1632dae2f tcwg_bmk-build.sh: Use "@build_num@" marker instead of "<build_num>"
adds 0e12cf5b3 tcwg_bmk-build.sh: Use "@build_num@" marker instead of "<build_num>"
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 (1632dae2f)
\
N -- N -- N refs/changes/63/30863/1 (0e12cf5b3)
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/63/30263/3
in repository toolchain/jenkins-scripts.
discards bf550484f [rr-many 6/N] Improve update_baseline
adds 975b084f9 [rr-many 6/N] Improve update_baseline
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 (bf550484f)
\
N -- N -- N refs/changes/63/30263/3 (975b084f9)
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/63/30263/2
in repository toolchain/jenkins-scripts.
discards 87b9a9d2d [rr-many 6/N] Improve update_baseline
new 213263208 [rr-many 6/N] Improve update_baseline
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 (87b9a9d2d)
\
N -- N -- N refs/changes/63/30263/2 (213263208)
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/63/30263/1
in repository toolchain/jenkins-scripts.
discards f60d65446 [rr-many 6/N] Improve update_baseline
new 3a794b979 [rr-many 6/N] Improve update_baseline
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 (f60d65446)
\
N -- N -- N refs/changes/63/30263/1 (3a794b979)
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/63/29463/2
in repository toolchain/jenkins-scripts.
discards 6282831f9 tcwg_kernel-bisect.sh: Add missing shift to process second se [...]
discards b55571754 tcwg_kernel-bisect.sh: Fix typo.
discards ff8464263 tcwg_kernel-build.sh: Fix typo.
adds 784ddf170 tcwg_kernel-build.sh: Fix typo.
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 (6282831f9)
\
N -- N -- N refs/changes/63/29463/2 (784ddf170)
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 | 249 --------------------------------------------------
1 file changed, 249 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/63/29463/1
in repository toolchain/jenkins-scripts.
discards 11a156661 tcwg_kernel-bisect.sh: Add missing shift to process second se [...]
discards 87c9f2d6c tcwg_kernel-bisect.sh: Fix typo.
discards 7980e7b79 round-robin.sh, tcwg_kernel-build.sh: Remove ${rr[git_read_only]}
new 8d1c4c36d round-robin.sh, tcwg_kernel-build.sh: Remove ${rr[git_read_only]}
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 (11a156661)
\
N -- N -- N refs/changes/63/29463/1 (8d1c4c36d)
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:
tcwg_kernel-bisect.sh | 249 --------------------------------------------------
1 file changed, 249 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/62/47262/1
in repository toolchain/jenkins-scripts.
discards 3644164ae pw-report.sh: Fix typo in previous commit
adds 9b2c936b3 pw-report.sh: Fix typo in previous commit
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 (3644164ae)
\
N -- N -- N refs/changes/62/47262/1 (9b2c936b3)
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/62/47062/2
in repository toolchain/jenkins-scripts.
discards f3d241583 round-robin-baseline.sh (rewrite_single_revision): Relax assert
discards 45385d075 tcwg-update-lnt-results.sh: Ignore tcwg_gnu build-only config [...]
adds ec5e03034 tcwg-update-lnt-results.sh: Ignore tcwg_gnu build-only 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 (f3d241583)
\
N -- N -- N refs/changes/62/47062/2 (ec5e03034)
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 | 630 -------------
round-robin-bisect.sh | 681 -------------
round-robin-notify.sh | 2414 -----------------------------------------------
3 files changed, 3725 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/62/47062/1
in repository toolchain/jenkins-scripts.
discards 2343b26da round-robin-baseline.sh (rewrite_single_revision): Relax assert
discards 4298c7568 round-robin.sh (build_abe check): Ignore known flaky tests in [...]
new 875051fcb round-robin.sh (build_abe check): Ignore known flaky tests in [...]
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 (2343b26da)
\
N -- N -- N refs/changes/62/47062/1 (875051fcb)
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 | 630 -------------
round-robin-bisect.sh | 681 -------------
round-robin-notify.sh | 2414 -----------------------------------------------
3 files changed, 3725 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.