This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/07/46407/1
in repository toolchain/jenkins-scripts.
discards b7c5c1a8a round-robin-notify.sh (print_mail_body): Fix formatting
discards f83ebb946 round-robin-notify.sh (generate_readme): List files as links
discards 0a2b874f4 round-robin-notify.sh: Fix pointer to BUILD_URL/artifact/artifacts
discards 91ab031c8 round-robin-notify.sh (generate_readme): Mention 00-sumfiles [...]
discards 00d405e04 round-robin-notify.sh (print_mail_body): Be more explicit whe [...]
discards 86e90f701 round-robin-notify.sh (generate_readme): Print list of files [...]
discards 612fd815a tcwg-lnt: Add patch to change color in daily report
adds 430d33e7c tcwg-lnt: Add patch to change color in daily report
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 (b7c5c1a8a)
\
N -- N -- N refs/changes/07/46407/1 (430d33e7c)
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 | 2314 -----------------------------------------------
3 files changed, 3562 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/07/46307/2
in repository toolchain/jenkins-scripts.
discards 6b4b56155 tcwg_gnu-build.sh: Fix comment
adds b848ab382 tcwg_gnu-build.sh: Fix comment
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 (6b4b56155)
\
N -- N -- N refs/changes/07/46307/2 (b848ab382)
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/07/46307/1
in repository toolchain/jenkins-scripts.
discards 462f14097 tcwg_gnu-build.sh: Fix comment
adds 7d6ed02f7 tcwg_gnu-build.sh: Fix comment
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 (462f14097)
\
N -- N -- N refs/changes/07/46307/1 (7d6ed02f7)
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/07/45407/1
in repository toolchain/jenkins-scripts.
discards 17a91075a round-robin-notify.sh: Fix previous commit
discards 7f4b459f9 round-robin-notify.sh: Re-create jira/ dir from new information
discards 56588aad4 round-robin-notify.sh (update_jira_card): Add components and [...]
discards 00b2e8b38 pw-report.sh: Update links to artifacts
adds f0567bb00 pw-report.sh: Update links to artifacts
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 (17a91075a)
\
N -- N -- N refs/changes/07/45407/1 (f0567bb00)
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 | 410 ------------
round-robin-bisect.sh | 653 --------------------
round-robin-notify.sh | 1572 -----------------------------------------------
3 files changed, 2635 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/07/44607/2
in repository toolchain/jenkins-scripts.
discards 0fc893f2f round-robin.sh: Fix "ERROR: case (4) in check_regression" errors
adds f87dcca44 round-robin.sh: Fix "ERROR: case (4) in check_regression" errors
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 (0fc893f2f)
\
N -- N -- N refs/changes/07/44607/2 (f87dcca44)
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/07/44607/1
in repository toolchain/jenkins-scripts.
discards 4c6f927d3 round-robin.sh: Fix "ERROR: case (4) in check_regression" errors
new e7d92939f round-robin.sh: Fix "ERROR: case (4) in check_regression" errors
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 (4c6f927d3)
\
N -- N -- N refs/changes/07/44607/1 (e7d92939f)
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/07/44507/3
in repository toolchain/jenkins-scripts.
discards cbbce909e Dashboard: Add a table for configuraations requested by Arm
adds b18bc9b01 Dashboard: Add a table for configuraations requested by Arm
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 (cbbce909e)
\
N -- N -- N refs/changes/07/44507/3 (b18bc9b01)
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/07/44507/2
in repository toolchain/jenkins-scripts.
discards 2fa681df6 Dashboard: Add a table for configuraations requested by Arm
new bcddc3f5e Dashboard: Add a table for configuraations requested by Arm
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 (2fa681df6)
\
N -- N -- N refs/changes/07/44507/2 (bcddc3f5e)
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/07/44507/1
in repository toolchain/jenkins-scripts.
discards b71d5714b Dashboard: Add a table for configuraations requested by Arm
new feccb3eee Dashboard: Add a table for configuraations requested by Arm
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 (b71d5714b)
\
N -- N -- N refs/changes/07/44507/1 (feccb3eee)
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/07/43807/1
in repository toolchain/jenkins-scripts.
discards 8afd908d3 Revert "tcwg-llvmbot: Don't start Graviton 3 workers"
adds f471b0134 Revert "tcwg-llvmbot: Don't start Graviton 3 workers"
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 (8afd908d3)
\
N -- N -- N refs/changes/07/43807/1 (f471b0134)
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.