This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/11/46511/1
in repository toolchain/jenkins-scripts.
discards 4bf93a11c round-robin-notify.sh (print_readme_link): Fix thinko with /* [...]
discards ca08ee86c tcwg_gnu-build.sh: Extract configure command line
new 26db146c5 tcwg_gnu-build.sh: Extract configure command line
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 (4bf93a11c)
\
N -- N -- N refs/changes/11/46511/1 (26db146c5)
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 | 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/11/46211/2
in repository toolchain/jenkins-scripts.
discards 4b28cab87 precommit-ssh-apply.sh: New script for testing precommit patches
adds 34ba7e101 precommit-ssh-apply.sh: New script for testing precommit patches
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 (4b28cab87)
\
N -- N -- N refs/changes/11/46211/2 (34ba7e101)
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/11/46211/1
in repository toolchain/jenkins-scripts.
discards 3789dbbae precommit-ssh-apply.sh: New script for testing precommit patches
adds 918e1dae3 precommit-ssh-apply.sh: New script for testing precommit patches
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 (3789dbbae)
\
N -- N -- N refs/changes/11/46211/1 (918e1dae3)
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/11/45711/2
in repository toolchain/jenkins-scripts.
discards f51ae4d13 round-robin-notify.sh (jira cards): Do not update closed cards
discards e764a676c round-robin-notify.sh (gnu_print_result): Add links to useful logs
discards 60d3d8798 round-robin-notify.sh (gnu_print_result): Improve --long version
discards 17d36081f round-robin-notify.sh (print_mail_body): Add more ways to con [...]
discards 03877dae5 jenkins-helpers.sh (describe_sha1): Improve describes for bin [...]
adds e498d7bff jenkins-helpers.sh (describe_sha1): Improve describes for bin [...]
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 (f51ae4d13)
\
N -- N -- N refs/changes/11/45711/2 (e498d7bff)
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 | 524 --------------
round-robin-bisect.sh | 678 ------------------
round-robin-notify.sh | 1786 -----------------------------------------------
3 files changed, 2988 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/11/45711/1
in repository toolchain/jenkins-scripts.
discards d37c7fb40 round-robin-notify.sh (jira cards): Do not update closed cards
discards ec9ae9bb3 round-robin-notify.sh (gnu_print_result): Add links to useful logs
discards 3dda0bb08 round-robin-notify.sh (gnu_print_result): Improve --long version
discards e29a02204 round-robin-notify.sh (print_mail_body): Add more ways to con [...]
discards c21c34105 round-robin-baseline.sh (rewrite_single_revision): Add assert
discards 197d50292 tcwg_gnu-build.sh: Bump minor version to update jira cards
adds ead51574c tcwg_gnu-build.sh: Bump minor version to update jira cards
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 (d37c7fb40)
\
N -- N -- N refs/changes/11/45711/1 (ead51574c)
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 | 524 --------------
round-robin-bisect.sh | 655 -----------------
round-robin-notify.sh | 1786 -----------------------------------------------
3 files changed, 2965 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/11/45511/1
in repository toolchain/jenkins-scripts.
discards a0f52b969 round-robin-bisect.sh: Improve trigger for subsequent builds
adds 97d17c9ea round-robin-bisect.sh: Improve trigger for subsequent builds
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 (a0f52b969)
\
N -- N -- N refs/changes/11/45511/1 (97d17c9ea)
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/11/45411/2
in repository toolchain/jenkins-scripts.
discards 764cc70f3 Revert "Revert "tcwg-update-llvmbot-containers.sh: Add silent [...]
adds bc22a3aa3 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 (764cc70f3)
\
N -- N -- N refs/changes/11/45411/2 (bc22a3aa3)
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/11/45411/1
in repository toolchain/jenkins-scripts.
discards 33bc562c6 Revert "Revert "tcwg-update-llvmbot-containers.sh: Add silent [...]
new 625228e05 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 (33bc562c6)
\
N -- N -- N refs/changes/11/45411/1 (625228e05)
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/11/45311/1
in repository toolchain/jenkins-scripts.
discards ff83363be Revert "tcwg-update-llvmbot-containers.sh: Add silent flang d [...]
adds d6c2af7c9 Revert "tcwg-update-llvmbot-containers.sh: Add silent flang d [...]
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 (ff83363be)
\
N -- N -- N refs/changes/11/45311/1 (d6c2af7c9)
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/11/45211/1
in repository toolchain/jenkins-scripts.
discards 85118b930 tcwg-benchmark-results.sh: Fix failing rsync
adds e582e4078 tcwg-benchmark-results.sh: Fix failing rsync
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 (85118b930)
\
N -- N -- N refs/changes/11/45211/1 (e582e4078)
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.