This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/62/34962/1
in repository toolchain/jenkins-scripts.
discards d9dae9777 tcwg-cleanup-stale-containers.sh
adds ac471d6f7 tcwg-cleanup-stale-containers.sh
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 (d9dae9777)
\
N -- N -- N refs/changes/62/34962/1 (ac471d6f7)
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/34862/1
in repository toolchain/jenkins-scripts.
discards 5bc4a8aa4 round-robin.sh: Handle Os vs Os LTO result IDs
discards 66cb02dc9 round-robin-bisect.sh: Improve output
discards a0e4a3728 tcwg-benchmark.sh: Minor fixes
adds 325a84296 tcwg-benchmark.sh: Minor fixes
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 (5bc4a8aa4)
\
N -- N -- N refs/changes/62/34862/1 (325a84296)
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 | 650 --------------------------------------------------
1 file changed, 650 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/62/33062/3
in repository toolchain/jenkins-scripts.
discards 95c5ba52a round-robin.sh: Optimize splitting builds to narrow regression
adds c6083ea28 round-robin.sh: Optimize splitting builds to narrow regression
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 (95c5ba52a)
\
N -- N -- N refs/changes/62/33062/3 (c6083ea28)
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/33062/2
in repository toolchain/jenkins-scripts.
discards 80612ae28 round-robin.sh: Optimize splitting builds to narrow regression
new 68725d298 round-robin.sh: Optimize splitting builds to narrow regression
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 (80612ae28)
\
N -- N -- N refs/changes/62/33062/2 (68725d298)
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/62/33062/1
in repository toolchain/jenkins-scripts.
discards f7fdfb2f6 round-robin.sh: Optimize splitting builds to narrow regression
new 2226f22eb round-robin.sh: Optimize splitting builds to narrow regression
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 (f7fdfb2f6)
\
N -- N -- N refs/changes/62/33062/1 (2226f22eb)
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/62/31962/1
in repository toolchain/jenkins-scripts.
discards 8d3cf8749 round-robin.sh, tcwg_gnu-build.sh: Fix check_binutils typo
adds 4ff5a57fa round-robin.sh, tcwg_gnu-build.sh: Fix check_binutils 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 (8d3cf8749)
\
N -- N -- N refs/changes/62/31962/1 (4ff5a57fa)
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/30862/1
in repository toolchain/jenkins-scripts.
discards b2bc6beff tcwg_bmk-build.sh: Main support for tcwg_bmk
adds 03092c971 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 (b2bc6beff)
\
N -- N -- N refs/changes/62/30862/1 (03092c971)
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/30262/3
in repository toolchain/jenkins-scripts.
discards 86b171c5f [rr-many 5/N] Update update_baseline
adds a5decb3d1 [rr-many 5/N] Update 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 (86b171c5f)
\
N -- N -- N refs/changes/62/30262/3 (a5decb3d1)
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/30262/2
in repository toolchain/jenkins-scripts.
discards e88222168 [rr-many 5/N] Update update_baseline
adds ab1f0c6d4 [rr-many 5/N] Update 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 (e88222168)
\
N -- N -- N refs/changes/62/30262/2 (ab1f0c6d4)
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/30262/1
in repository toolchain/jenkins-scripts.
discards a0ff41360 [rr-many 5/N] Update update_baseline
adds 561afc61e [rr-many 5/N] Update 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 (a0ff41360)
\
N -- N -- N refs/changes/62/30262/1 (561afc61e)
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.