This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/05/39305/2
in repository toolchain/jenkins-scripts.
discards 287675d53 tcwg_bmk-build.sh: Cleanup
adds f0838ebb7 tcwg_bmk-build.sh: Cleanup
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 (287675d53)
\
N -- N -- N refs/changes/05/39305/2 (f0838ebb7)
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/05/39305/1
in repository toolchain/jenkins-scripts.
discards 4341988e5 tcwg_bmk-build.sh: Cleanup
adds 054236639 tcwg_bmk-build.sh: Cleanup
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 (4341988e5)
\
N -- N -- N refs/changes/05/39305/1 (054236639)
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/05/37405/2
in repository toolchain/jenkins-scripts.
discards 499beadee round-robin-bisect.sh: Make handling of unsuccessful bisects [...]
discards 36aa35cac round-robin-bisect.sh: Make code to trigger follow-up builds [...]
discards d04c755cb round-robin-bisect.sh: Make logic of handling successful bise [...]
discards 8bdc7c170 round-robin-bisect.sh: Simplify filtering of interesting commits
discards a9ee3b7ff tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
adds e1b7cb695 tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
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 (499beadee)
\
N -- N -- N refs/changes/05/37405/2 (e1b7cb695)
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 | 718 --------------------------------------------------
1 file changed, 718 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/05/37405/1
in repository toolchain/jenkins-scripts.
discards fbdf19b02 round-robin-bisect.sh: Make handling of unsuccessful bisects [...]
discards 36aa35cac round-robin-bisect.sh: Make code to trigger follow-up builds [...]
discards d04c755cb round-robin-bisect.sh: Make logic of handling successful bise [...]
discards 8bdc7c170 round-robin-bisect.sh: Simplify filtering of interesting commits
discards a9ee3b7ff tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
adds e1b7cb695 tcwg_bmk-build.sh: Update sysroot path after sysroot changes in ABE
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 (fbdf19b02)
\
N -- N -- N refs/changes/05/37405/1 (e1b7cb695)
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 | 718 --------------------------------------------------
1 file changed, 718 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/05/35205/4
in repository toolchain/jenkins-scripts.
discards a792a1d55 tcwg_bmk-build/tcwg_gnu-build: Add traceback printing
adds 2e2003cb8 tcwg_bmk-build/tcwg_gnu-build: Add traceback printing
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 (a792a1d55)
\
N -- N -- N refs/changes/05/35205/4 (2e2003cb8)
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/05/35205/3
in repository toolchain/jenkins-scripts.
discards c7e68ac7f tcwg_bmk-build/tcwg_gnu-build: Add traceback printing
adds 1d86e4782 tcwg_bmk-build/tcwg_gnu-build: Add traceback printing
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 (c7e68ac7f)
\
N -- N -- N refs/changes/05/35205/3 (1d86e4782)
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/05/35205/2
in repository toolchain/jenkins-scripts.
discards f8b8c4986 tcwg_bmk-build/tcwg_gnu-build: Add traceback printing
new 14782324c tcwg_bmk-build/tcwg_gnu-build: Add traceback printing
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 (f8b8c4986)
\
N -- N -- N refs/changes/05/35205/2 (14782324c)
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/05/35205/1
in repository toolchain/jenkins-scripts.
discards 79f2e974a tcwg_bmk-build/tcwg_gnu-build: Add traceback printing
new b2b243710 tcwg_bmk-build/tcwg_gnu-build: Add traceback printing
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 (79f2e974a)
\
N -- N -- N refs/changes/05/35205/1 (b2b243710)
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/05/33005/1
in repository toolchain/jenkins-scripts.
discards 2dc4fca2b jenkins-helpers.sh: Add a timeout for "ssh $board true" in wa [...]
adds ea22993d8 jenkins-helpers.sh: Add a timeout for "ssh $board true" in wa [...]
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 (2dc4fca2b)
\
N -- N -- N refs/changes/05/33005/1 (ea22993d8)
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/05/30905/1
in repository toolchain/jenkins-scripts.
discards 48b2da64c tcwg_kernel-bisect.sh: Remove
discards 9fb073a48 round-robin-bisect.sh: Create, as a copy of tcwg_kernel-bisect.sh
discards 1c327bc84 tcwg_bmk-build.sh: Main support for tcwg_bmk
adds 268d06fa3 tcwg_bmk-build.sh: Main support for tcwg_bmk
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 (48b2da64c)
\
N -- N -- N refs/changes/05/30905/1 (268d06fa3)
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 | 484 --------------------------------------------------
1 file changed, 484 deletions(-)
delete mode 100755 round-robin-bisect.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.