This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/72/46372/13
in repository toolchain/jenkins-scripts.
discards 196cf6c96 round-robin-notify.sh (release_gcc_testresults_files): Rely o [...]
discards a29b9db62 round-robin-notify.sh (gnu_generate_extra_details): Extract c [...]
discards 6931499fd round-robin-notify.sh (print_readme_link): Fix thinko with /* [...]
discards 9f0b332e8 pw-helpers.sh (pw_deinit): Handle manual precommit testing
adds e232a26a3 pw-helpers.sh (pw_deinit): Handle manual precommit testing
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 (196cf6c96)
\
N -- N -- N refs/changes/72/46372/13 (e232a26a3)
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 | 584 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2360 -----------------------------------------------
3 files changed, 3630 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/72/46372/12
in repository toolchain/jenkins-scripts.
discards ab44e0362 round-robin-notify.sh (release_gcc_testresults_files): Rely o [...]
discards c54e3dbb5 round-robin-notify.sh (gnu_generate_extra_details): Extract c [...]
discards 9f0b332e8 pw-helpers.sh (pw_deinit): Handle manual precommit testing
adds e232a26a3 pw-helpers.sh (pw_deinit): Handle manual precommit testing
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 (ab44e0362)
\
N -- N -- N refs/changes/72/46372/12 (e232a26a3)
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 | 584 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2360 -----------------------------------------------
3 files changed, 3630 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/72/46372/11
in repository toolchain/jenkins-scripts.
discards 38b36ffb0 round-robin-notify.sh (release_gcc_testresults_files): Rely o [...]
discards d26276887 round-robin-notify.sh (gnu_generate_extra_details): Extract c [...]
discards 9f0b332e8 pw-helpers.sh (pw_deinit): Handle manual precommit testing
adds e232a26a3 pw-helpers.sh (pw_deinit): Handle manual precommit testing
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 (38b36ffb0)
\
N -- N -- N refs/changes/72/46372/11 (e232a26a3)
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 | 584 ------------
round-robin-bisect.sh | 686 --------------
round-robin-notify.sh | 2360 -----------------------------------------------
3 files changed, 3630 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/72/46372/10
in repository toolchain/jenkins-scripts.
discards d60999d48 round-robin-notify.sh (release_gcc_testresults_files): Rely o [...]
discards e705115fb round-robin-notify.sh (gnu_generate_extra_details): Extract c [...]
discards b620557c3 round-robin-notify.ah (print_readme_link): Add /*view*/ if needed
discards c75da0386 lnt-utils.sh: Disable debug traces in a too verbose function
adds fa44b4de5 lnt-utils.sh: Disable debug traces in a too verbose function
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 (d60999d48)
\
N -- N -- N refs/changes/72/46372/10 (fa44b4de5)
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 | 567 ------------
round-robin-bisect.sh | 681 --------------
round-robin-notify.sh | 2358 -----------------------------------------------
3 files changed, 3606 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/72/46372/1
in repository toolchain/jenkins-scripts.
discards 7916c6ebb round-robin-notify.sh (release_gcc_testresults_files): Rely o [...]
discards dd0f2d7c4 round-robin-notify.sh: Point directly to BUILD_URL/artifact/a [...]
discards fb752d67b round-robin-notify.sh (release_testresults_files): Call calcu [...]
discards 46d25e6d8 round-robin.sh (build_abe): Do not update LAST_UPDATED and gc [...]
adds 62494a99a round-robin.sh (build_abe): Do not update LAST_UPDATED and gc [...]
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 (7916c6ebb)
\
N -- N -- N refs/changes/72/46372/1 (62494a99a)
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 | 567 ------------
round-robin-bisect.sh | 681 --------------
round-robin-notify.sh | 2291 -----------------------------------------------
3 files changed, 3539 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/72/46272/2
in repository toolchain/jenkins-scripts.
discards 3104eb768 round-robin.sh (build_abe): Move testresults files to jenkins/
adds 2fe999ccb round-robin.sh (build_abe): Move testresults files to jenkins/
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 (3104eb768)
\
N -- N -- N refs/changes/72/46272/2 (2fe999ccb)
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/72/46272/1
in repository toolchain/jenkins-scripts.
discards 214a8ebbc round-robin.sh (build_abe): Move testresults files to jenkins/
adds 997914700 round-robin.sh (build_abe): Move testresults files to jenkins/
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 (214a8ebbc)
\
N -- N -- N refs/changes/72/46272/1 (997914700)
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/72/45772/1
in repository toolchain/jenkins-scripts.
discards 9c4c80a6b Revert "Revert "tcwg-update-llvmbot-containers.sh: Add silent [...]
adds e6ca3d772 Revert "Revert "tcwg-update-llvmbot-containers.sh: Add silent [...]
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 (9c4c80a6b)
\
N -- N -- N refs/changes/72/45772/1 (e6ca3d772)
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/72/45672/1
in repository toolchain/jenkins-scripts.
discards f6dae06a5 jenkins-helpers.sh (git_annex_upload): Allow access to bmk results
adds 75fd5372f jenkins-helpers.sh (git_annex_upload): Allow access to bmk 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 (f6dae06a5)
\
N -- N -- N refs/changes/72/45672/1 (75fd5372f)
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/72/45572/2
in repository toolchain/jenkins-scripts.
discards c7c54410b round-robin-notify.sh (post_interesting_commits): Use gitolite
adds c264985e7 round-robin-notify.sh (post_interesting_commits): Use gitolite
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 (c7c54410b)
\
N -- N -- N refs/changes/72/45572/2 (c264985e7)
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.