This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/90/47290/1
in repository toolchain/jenkins-scripts.
discards f7c35f7d9 generate-cimonitor-dashboard.py: fixing my ridiculous mistake
new 5d9c0f95c generate-cimonitor-dashboard.py: fixing my ridiculous mistake
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 (f7c35f7d9)
\
N -- N -- N refs/changes/90/47290/1 (5d9c0f95c)
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/90/47190/1
in repository toolchain/jenkins-scripts.
discards ebc080c31 round-robin-bisect.sh: typo for trigger files
discards 0c4c3e9ee round-robin-bisect.sh: Adjust trigger files in case of dynami [...]
discards f66fabd79 tcwg_chromium-build.sh: component_to_update inherit from base [...]
adds 901278dbd tcwg_chromium-build.sh: component_to_update inherit from base [...]
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 (ebc080c31)
\
N -- N -- N refs/changes/90/47190/1 (901278dbd)
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 | 650 -------------
round-robin-bisect.sh | 742 ---------------
round-robin-notify.sh | 2419 -----------------------------------------------
3 files changed, 3811 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/90/46690/2
in repository toolchain/jenkins-scripts.
discards 604cff689 tcwg-update-lnt-results.sh: Reworked
adds 193190b23 tcwg-update-lnt-results.sh: Reworked
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 (604cff689)
\
N -- N -- N refs/changes/90/46690/2 (193190b23)
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/90/46690/1
in repository toolchain/jenkins-scripts.
discards bd7c21cfa tcwg-update-lnt-results.sh: Reworked
new d7ad1641e tcwg-update-lnt-results.sh: Reworked
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 (bd7c21cfa)
\
N -- N -- N refs/changes/90/46690/1 (d7ad1641e)
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/90/46590/3
in repository toolchain/jenkins-scripts.
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 (4a1a20aed)
\
N -- N -- N refs/changes/90/46590/3 (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 | 611 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2364 -----------------------------------------------
3 files changed, 3661 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/90/46590/2
in repository toolchain/jenkins-scripts.
discards 3a1697f7e round-robin-notify.sh (gnu_print_result): Remove "Results Sum [...]
discards 065209a71 round-robin-notify.sh (gnu_print_result): Add configure/make [...]
discards 41591de5c round-robin-notify.sh (release_gcc_testresults_files): Fix ha [...]
discards d0a72f55b round-robin.sh (build_abe): Do not send results for "fast_che [...]
adds 81599b3db round-robin.sh (build_abe): Do not send results for "fast_che [...]
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 (3a1697f7e)
\
N -- N -- N refs/changes/90/46590/2 (81599b3db)
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 | 605 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2364 -----------------------------------------------
3 files changed, 3655 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/90/46590/1
in repository toolchain/jenkins-scripts.
discards 13890df57 round-robin-notify.sh (gnu_print_result): Remove "Results Sum [...]
discards 971e1abce round-robin-notify.sh (gnu_print_result): Add configure/make [...]
discards 6bce9f834 round-robin.sh (build_abe): Enable maitainer_mode in precommi [...]
new 1bb9f17e6 round-robin.sh (build_abe): Enable maitainer_mode in precommi [...]
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 (13890df57)
\
N -- N -- N refs/changes/90/46590/1 (1bb9f17e6)
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-baseline.sh | 605 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2364 -----------------------------------------------
3 files changed, 3655 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/90/46290/2
in repository toolchain/jenkins-scripts.
discards 906087e33 round-robin.sh (build_abe): Fix move of testresults files to [...]
adds abb9008a8 round-robin.sh (build_abe): Fix move of testresults files to [...]
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 (906087e33)
\
N -- N -- N refs/changes/90/46290/2 (abb9008a8)
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/90/46290/1
in repository toolchain/jenkins-scripts.
discards 135884ff4 round-robin.sh (build_abe): Fix move of testresults files to [...]
new c7be48f88 round-robin.sh (build_abe): Fix move of testresults files to [...]
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 (135884ff4)
\
N -- N -- N refs/changes/90/46290/1 (c7be48f88)
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/90/45890/1
in repository toolchain/jenkins-scripts.
discards 2e9faa156 lnt-utils.sh: do nothing when there is no sum file
adds 15de24190 lnt-utils.sh: do nothing when there is no sum file
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 (2e9faa156)
\
N -- N -- N refs/changes/90/45890/1 (15de24190)
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.