This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/94/30594/1
in repository toolchain/jenkins-scripts.
discards 0da0e554b tcwg_gnu-build.sh: Update after merge.
adds 10c09ebd4 tcwg_gnu-build.sh: Update after merge.
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 (0da0e554b)
\
N -- N -- N refs/changes/94/30594/1 (10c09ebd4)
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/93/47093/3
in repository toolchain/jenkins-scripts.
discards bba16eb36 icommits-stats.py: Helper script to gather some statistics
adds 2aede660c icommits-stats.py: Helper script to gather some statistics
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 (bba16eb36)
\
N -- N -- N refs/changes/93/47093/3 (2aede660c)
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/93/47093/2
in repository toolchain/jenkins-scripts.
discards 2ca89d4b2 icommits-stats.py: Helper script to gather some statistics
new d62def30f icommits-stats.py: Helper script to gather some statistics
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 (2ca89d4b2)
\
N -- N -- N refs/changes/93/47093/2 (d62def30f)
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/93/47093/1
in repository toolchain/jenkins-scripts.
discards b3afc46bf icommits-stats.py: Helper script to gather some statistics
adds 48a4909d7 icommits-stats.py: Helper script to gather some statistics
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 (b3afc46bf)
\
N -- N -- N refs/changes/93/47093/1 (48a4909d7)
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/93/46993/1
in repository toolchain/jenkins-scripts.
discards be4876d90 round-robin-notify.sh (gnu_print_result): Fix typo
discards 379325d6a lnt-utils.sh (generate_lnt_gnu_check_report): Fix typo
adds 9154f0705 lnt-utils.sh (generate_lnt_gnu_check_report): Fix 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 (be4876d90)
\
N -- N -- N refs/changes/93/46993/1 (9154f0705)
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-baseline.sh | 624 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2409 -----------------------------------------------
3 files changed, 3719 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.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/93/46693/3
in repository toolchain/jenkins-scripts.
discards b3bbc95ba tcwg-cleanup-stale-results.sh: Now cleanup base-artifacts and [...]
adds cd1bca98d tcwg-cleanup-stale-results.sh: Now cleanup base-artifacts and [...]
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 (b3bbc95ba)
\
N -- N -- N refs/changes/93/46693/3 (cd1bca98d)
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/93/46693/2
in repository toolchain/jenkins-scripts.
discards f6cf31454 tcwg-cleanup-stale-results.sh: Now cleanup base-artifacts and [...]
new 7a62c6686 tcwg-cleanup-stale-results.sh: Now cleanup base-artifacts and [...]
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 (f6cf31454)
\
N -- N -- N refs/changes/93/46693/2 (7a62c6686)
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/93/46693/1
in repository toolchain/jenkins-scripts.
discards aae78ad42 tcwg-cleanup-stale-results.sh: Now cleanup base-artifacts and [...]
new dc54ad4ff tcwg-cleanup-stale-results.sh: Now cleanup base-artifacts and [...]
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 (aae78ad42)
\
N -- N -- N refs/changes/93/46693/1 (dc54ad4ff)
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/93/46593/2
in repository toolchain/jenkins-scripts.
discards 5f803c6c5 round-robin-baseline.sh (push_baseline): Optimize rewrite case
discards 97148fca4 round-robin.sh (build_abe): Remove testresults/ before creating it
adds 5aaddda9f round-robin.sh (build_abe): Remove testresults/ before creating it
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 (5f803c6c5)
\
N -- N -- N refs/changes/93/46593/2 (5aaddda9f)
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-baseline.sh | 615 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2364 -----------------------------------------------
3 files changed, 3665 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.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/93/46593/1
in repository toolchain/jenkins-scripts.
discards 16451e57f round-robin-baseline.sh (push_baseline): Optimize rewrite case
discards 4a1a20aed round-robin-notify.sh (gnu_print_result): Remove "Results Sum [...]
discards 73fc9f13c round-robin-notify.sh (gnu_print_result): Add configure/make [...]
discards a39df41b8 tcwg_gnu-build.sh: Upgrading version to update LNT dashboard [...]
adds 928ac6202 tcwg_gnu-build.sh: Upgrading version to update LNT dashboard [...]
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 (16451e57f)
\
N -- N -- N refs/changes/93/46593/1 (928ac6202)
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-baseline.sh | 606 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2364 -----------------------------------------------
3 files changed, 3656 deletions(-)
delete mode 100755 round-robin-baseline.sh
delete mode 100755 round-robin-bisect.sh
delete mode 100755 round-robin-notify.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.