This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/58/36958/1
in repository toolchain/jenkins-scripts.
discards dcf7d18f6 Revert "tcwg_{bmk,gnu,kernel}-build.sh: Update to not overrid [...]
adds 91ebdffc9 Revert "tcwg_{bmk,gnu,kernel}-build.sh: Update to not overrid [...]
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 (dcf7d18f6)
\
N -- N -- N refs/changes/58/36958/1 (91ebdffc9)
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/58/35358/1
in repository toolchain/jenkins-scripts.
discards 9f4e89dd0 round-robin.sh: Fix one more artifact in build_abe()
adds fb2e40494 round-robin.sh: Fix one more artifact in build_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 (9f4e89dd0)
\
N -- N -- N refs/changes/58/35358/1 (fb2e40494)
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/58/34058/1
in repository toolchain/jenkins-scripts.
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 (4f9dedf88)
\
N -- N -- N refs/changes/58/34058/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:
--
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/58/33958/3
in repository toolchain/jenkins-scripts.
discards a8f13708d round-robin.sh: Report build regression only if build result [...]
adds 2b592d38c round-robin.sh: Report build regression only if build result [...]
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 (a8f13708d)
\
N -- N -- N refs/changes/58/33958/3 (2b592d38c)
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/58/33958/2
in repository toolchain/jenkins-scripts.
discards 5e096aecd round-robin.sh: Report build regression only if build result [...]
adds 4539fc4d0 round-robin.sh: Report build regression only if build result [...]
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 (5e096aecd)
\
N -- N -- N refs/changes/58/33958/2 (4539fc4d0)
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/58/33958/1
in repository toolchain/jenkins-scripts.
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 (189ad7cc1)
\
N -- N -- N refs/changes/58/33958/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:
--
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/58/30458/1
in repository toolchain/jenkins-scripts.
discards bdbd1f2c3 tcwg_kernel-build.sh: Restrict linking with LLD to defconfig
adds 47c1b8759 tcwg_kernel-build.sh: Restrict linking with LLD to defconfig
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 (bdbd1f2c3)
\
N -- N -- N refs/changes/58/30458/1 (47c1b8759)
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/58/30258/3
in repository toolchain/jenkins-scripts.
discards 2689c8ee9 [rr-many 1/N]: Support testing multiple projects in the same build
adds 701df7c5c [rr-many 1/N]: Support testing multiple projects in the same build
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 (2689c8ee9)
\
N -- N -- N refs/changes/58/30258/3 (701df7c5c)
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/58/30258/2
in repository toolchain/jenkins-scripts.
discards 70f4a6217 [rr-many 1/N]: Support testing multiple projects in the same build
adds c30eb3f8e [rr-many 1/N]: Support testing multiple projects in the same build
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 (70f4a6217)
\
N -- N -- N refs/changes/58/30258/2 (c30eb3f8e)
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/58/30258/1
in repository toolchain/jenkins-scripts.
discards 2fa4f7225 [rr-many 1/N]: Support testing multiple projects in the same build
adds afe37972b [rr-many 1/N]: Support testing multiple projects in the same build
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 (2fa4f7225)
\
N -- N -- N refs/changes/58/30258/1 (afe37972b)
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.