This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/59/35059/2
in repository toolchain/jenkins-scripts.
discards 86f492f54 jenkins-helpers.sh: Add log URL when running a step
adds 6cb2b9067 jenkins-helpers.sh: Add log URL when running a step
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 (86f492f54)
\
N -- N -- N refs/changes/59/35059/2 (6cb2b9067)
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/59/35059/1
in repository toolchain/jenkins-scripts.
discards c8a3a87fd jenkins-helpers.sh: Add log URL when running a step
new 6b2729c0a jenkins-helpers.sh: Add log URL when running a step
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 (c8a3a87fd)
\
N -- N -- N refs/changes/59/35059/1 (6b2729c0a)
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/59/34059/2
in repository toolchain/jenkins-scripts.
discards 3dc4106ad round-robin-bisect.sh: Reduce verbosity of interesting-commits loop
discards 4f9dedf88 tcwg_bmk-build.sh: Better handle LTO results
adds d857330d5 tcwg_bmk-build.sh: Better handle LTO results
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 (3dc4106ad)
\
N -- N -- N refs/changes/59/34059/2 (d857330d5)
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 | 608 --------------------------------------------------
1 file changed, 608 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/59/34059/1
in repository toolchain/jenkins-scripts.
discards 213cdfc61 round-robin-bisect.sh: Reduce verbosity of interesting-commits loop
discards 4f9dedf88 tcwg_bmk-build.sh: Better handle LTO results
adds d857330d5 tcwg_bmk-build.sh: Better handle LTO results
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 (213cdfc61)
\
N -- N -- N refs/changes/59/34059/1 (d857330d5)
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 | 607 --------------------------------------------------
1 file changed, 607 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/59/33959/4
in repository toolchain/jenkins-scripts.
discards d12b504ac tcwg_gnu-build.sh: Make top_artifacts is an absolute directory
adds 11777434d tcwg_gnu-build.sh: Make top_artifacts is an absolute directory
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 (d12b504ac)
\
N -- N -- N refs/changes/59/33959/4 (11777434d)
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/59/33959/3
in repository toolchain/jenkins-scripts.
discards 35ec1986f tcwg_gnu-build.sh: Make top_artifacts is an absolute directory
new a097a36f1 tcwg_gnu-build.sh: Make top_artifacts is an absolute directory
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 (35ec1986f)
\
N -- N -- N refs/changes/59/33959/3 (a097a36f1)
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/59/33959/2
in repository toolchain/jenkins-scripts.
discards 52037860c tcwg_gnu-build.sh: Make top_artifacts is an absolute directory
new 04f5f9c5c tcwg_gnu-build.sh: Make top_artifacts is an absolute directory
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 (52037860c)
\
N -- N -- N refs/changes/59/33959/2 (04f5f9c5c)
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/59/33959/1
in repository toolchain/jenkins-scripts.
discards 64efca770 round-robin-bisect.sh: Use top_artifacts rather than rel_arti [...]
discards 189ad7cc1 round-robin.sh: No build regression if build result is the sa [...]
new 6c6fabe9e round-robin.sh: No build regression if build result is the sa [...]
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 (64efca770)
\
N -- N -- N refs/changes/59/33959/1 (6c6fabe9e)
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-bisect.sh | 598 --------------------------------------------------
1 file changed, 598 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/59/33559/5
in repository toolchain/jenkins-scripts.
discards 63024d990 round-robin.sh: Create branch in interesting-commits for cust [...]
adds 401d482ab round-robin.sh: Create branch in interesting-commits for cust [...]
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 (63024d990)
\
N -- N -- N refs/changes/59/33559/5 (401d482ab)
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/59/33559/4
in repository toolchain/jenkins-scripts.
discards 76f04342f round-robin.sh: Create branch in interesting-commits for cust [...]
adds 2a0a816df round-robin.sh: Create branch in interesting-commits for cust [...]
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 (76f04342f)
\
N -- N -- N refs/changes/59/33559/4 (2a0a816df)
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.