This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/73/41973/1
in repository toolchain/jenkins-scripts.
discards b5da24783 tcwg_aosp-build.sh: Initial version
adds 3cab8b4b1 tcwg_aosp-build.sh: Initial version
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 (b5da24783)
\
N -- N -- N refs/changes/73/41973/1 (3cab8b4b1)
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/73/39773/1
in repository toolchain/jenkins-scripts.
discards 20cae05c7 round-robin.sh (no_build_regression_p): Make more robust
adds 1ff758ca3 round-robin.sh (no_build_regression_p): Make more robust
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 (20cae05c7)
\
N -- N -- N refs/changes/73/39773/1 (1ff758ca3)
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/73/39673/1
in repository toolchain/jenkins-scripts.
discards 8761363ce round-robin.sh: Remove handling of "==rr[update_baseline] rebase"
adds adb6ab8b9 round-robin.sh: Remove handling of "==rr[update_baseline] rebase"
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 (8761363ce)
\
N -- N -- N refs/changes/73/39673/1 (adb6ab8b9)
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/73/39473/1
in repository toolchain/jenkins-scripts.
discards 5ae5d906c round-robin-bisect.sh: Rebase on gcc-compare-results:master b [...]
discards b69c914ac round-robin.sh (build_abe): Improve check_gdb workaround
adds 3715f725f round-robin.sh (build_abe): Improve check_gdb workaround
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 (5ae5d906c)
\
N -- N -- N refs/changes/73/39473/1 (3715f725f)
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-bisect.sh | 851 --------------------------------------------------
1 file changed, 851 deletions(-)
delete mode 100755 round-robin-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/73/39173/1
in repository toolchain/jenkins-scripts.
discards 8e8b037ae round-robin-bisect.sh: Update email preferences
discards 9b02eebd5 round-robin-bisect.sh: Fix line breaks
discards e599832c4 round-robin-bisect.sh: Save/restore baseline state
adds 6d14ec972 round-robin-bisect.sh: Save/restore baseline state
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 (8e8b037ae)
\
N -- N -- N refs/changes/73/39173/1 (6d14ec972)
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-bisect.sh | 782 --------------------------------------------------
1 file changed, 782 deletions(-)
delete mode 100755 round-robin-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/73/38773/2
in repository toolchain/jenkins-scripts.
discards c7650d5bd tcwg_bmk-build.sh: Update bmk job name
adds 589dafc6d tcwg_bmk-build.sh: Update bmk job name
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 (c7650d5bd)
\
N -- N -- N refs/changes/73/38773/2 (589dafc6d)
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/73/38773/1
in repository toolchain/jenkins-scripts.
discards 3354e18a6 Revert "Revert "tcwg_bmk-build.sh: Switch TK1 and TX1 benchma [...]
new efc8ad197 Revert "Revert "tcwg_bmk-build.sh: Switch TK1 and TX1 benchma [...]
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 (3354e18a6)
\
N -- N -- N refs/changes/73/38773/1 (efc8ad197)
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/73/37773/1
in repository toolchain/jenkins-scripts.
discards ebecd4490 tcwg_kernel-build.sh: Use LLD for all LLVM configurations
adds 22365e759 tcwg_kernel-build.sh: Use LLD for all LLVM configurations
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 (ebecd4490)
\
N -- N -- N refs/changes/73/37773/1 (22365e759)
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/73/36373/2
in repository toolchain/jenkins-scripts.
discards 1d5976a5b jenkins-helpers.sh: Split $EXPECTED_EXIT into $INTERNAL_FAIL
adds 01247f9c2 jenkins-helpers.sh: Split $EXPECTED_EXIT into $INTERNAL_FAIL
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 (1d5976a5b)
\
N -- N -- N refs/changes/73/36373/2 (01247f9c2)
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/73/36373/1
in repository toolchain/jenkins-scripts.
discards 3f4f19600 jenkins-helpers.sh: Split $EXPECTED_EXIT into $INTERNAL_FAIL
adds 099b1caa9 jenkins-helpers.sh: Split $EXPECTED_EXIT into $INTERNAL_FAIL
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 (3f4f19600)
\
N -- N -- N refs/changes/73/36373/1 (099b1caa9)
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.