This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/57/44557/1
in repository toolchain/jenkins-scripts.
discards d6439768e round-robin-notify.sh: Replace full commit by its link
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 (d6439768e)
\
N -- N -- N refs/changes/57/44557/1 (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:
round-robin-baseline.sh | 166 -------
round-robin-bisect.sh | 653 ------------------------
round-robin-notify.sh | 1264 -----------------------------------------------
3 files changed, 2083 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/57/44357/2
in repository toolchain/jenkins-scripts.
discards c006b805d jenkins-helpers.sh (clone_or_update_repo_no_checkout): Make m [...]
adds c1bb78787 jenkins-helpers.sh (clone_or_update_repo_no_checkout): Make m [...]
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 (c006b805d)
\
N -- N -- N refs/changes/57/44357/2 (c1bb78787)
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/57/44357/1
in repository toolchain/jenkins-scripts.
discards 7d8e82c5f jenkins-helpers.sh (clone_or_update_repo_no_checkout): Make m [...]
adds 8aad4ed3a jenkins-helpers.sh (clone_or_update_repo_no_checkout): Make m [...]
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 (7d8e82c5f)
\
N -- N -- N refs/changes/57/44357/1 (8aad4ed3a)
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/57/44157/3
in repository toolchain/jenkins-scripts.
discards 4639f4b46 tcwg_gnu-build.sh / no_regression_p: Terminate results.regres [...]
adds 448c81247 tcwg_gnu-build.sh / no_regression_p: Terminate results.regres [...]
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 (4639f4b46)
\
N -- N -- N refs/changes/57/44157/3 (448c81247)
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/57/44157/2
in repository toolchain/jenkins-scripts.
discards 4c612ef19 tcwg_gnu-build.sh / no_regression_p: Terminate results.regres [...]
new 440aeabb7 tcwg_gnu-build.sh / no_regression_p: Terminate results.regres [...]
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 (4c612ef19)
\
N -- N -- N refs/changes/57/44157/2 (440aeabb7)
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/57/44157/1
in repository toolchain/jenkins-scripts.
discards 4c98eac1e tcwg_gnu-build.sh / no_regression_p: Terminate results.regres [...]
new 9f09cedfd tcwg_gnu-build.sh / no_regression_p: Terminate results.regres [...]
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 (4c98eac1e)
\
N -- N -- N refs/changes/57/44157/1 (9f09cedfd)
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/57/43257/2
in repository toolchain/jenkins-scripts.
discards 656c257d8 tcwg_gnu-build.sh: Enable regression checking for check-binutils
adds 97ead98a8 tcwg_gnu-build.sh: Enable regression checking for check-binutils
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 (656c257d8)
\
N -- N -- N refs/changes/57/43257/2 (97ead98a8)
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/57/43257/1
in repository toolchain/jenkins-scripts.
discards 3302b832f tcwg_gnu-build.sh: Enable regression checking for check-binutils
new 54911d059 tcwg_gnu-build.sh: Enable regression checking for check-binutils
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 (3302b832f)
\
N -- N -- N refs/changes/57/43257/1 (54911d059)
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/57/42057/1
in repository toolchain/jenkins-scripts.
discards 8a8a20ea3 dashboard-generate-squad.sh: error if no TCWG_SQUAD_TOKEN defined
adds 631ad2489 dashboard-generate-squad.sh: error if no TCWG_SQUAD_TOKEN defined
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 (8a8a20ea3)
\
N -- N -- N refs/changes/57/42057/1 (631ad2489)
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/57/41957/2
in repository toolchain/jenkins-scripts.
discards 91d632918 tcwg_bmk-build.sh: Fix reporting for code-size metric
adds c53425721 tcwg_bmk-build.sh: Fix reporting for code-size metric
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 (91d632918)
\
N -- N -- N refs/changes/57/41957/2 (c53425721)
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.