This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/36/46836/3
in repository toolchain/jenkins-scripts.
discards 59d14125f tcwg-lnt/schemas: rename exec field into execution
adds b622cdcfb tcwg-lnt/schemas: rename exec field into execution
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 (59d14125f)
\
N -- N -- N refs/changes/36/46836/3 (b622cdcfb)
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/36/46836/2
in repository toolchain/jenkins-scripts.
discards db8911420 tcwg-lnt/schemas: rename exec field into execution
adds e6bb41e7c tcwg-lnt/schemas: rename exec field into execution
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 (db8911420)
\
N -- N -- N refs/changes/36/46836/2 (e6bb41e7c)
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/36/46836/1
in repository toolchain/jenkins-scripts.
discards aa504b6c3 tcwg-lnt/schemas: rename exec field into execution
adds 1d4b38dcb tcwg-lnt/schemas: rename exec field into execution
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 (aa504b6c3)
\
N -- N -- N refs/changes/36/46836/1 (1d4b38dcb)
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/36/45136/2
in repository toolchain/jenkins-scripts.
discards 90643ce55 tcwg_gnu-build.sh: Remove --with-arch option for thumb_m33_eabi
adds d3e9c2a9c tcwg_gnu-build.sh: Remove --with-arch option for thumb_m33_eabi
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 (90643ce55)
\
N -- N -- N refs/changes/36/45136/2 (d3e9c2a9c)
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/36/45136/1
in repository toolchain/jenkins-scripts.
discards ddeb73d0d tcwg_gnu-build.sh: Remove --with-arch option for thumb_m33_eabi
adds f9fe8ae13 tcwg_gnu-build.sh: Remove --with-arch option for thumb_m33_eabi
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 (ddeb73d0d)
\
N -- N -- N refs/changes/36/45136/1 (f9fe8ae13)
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/36/44936/1
in repository toolchain/jenkins-scripts.
discards a6c31dd67 round-robin-baseline.sh: Fix perf record directory
discards 50ffd5cac tcwg_bmk-build.sh: Fix perf record directory
adds 8969fd1ff tcwg_bmk-build.sh: Fix perf record directory
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 (a6c31dd67)
\
N -- N -- N refs/changes/36/44936/1 (8969fd1ff)
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 | 409 -------------
round-robin-bisect.sh | 653 ---------------------
round-robin-notify.sh | 1496 -----------------------------------------------
3 files changed, 2558 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/36/44536/1
in repository toolchain/jenkins-scripts.
discards dabf6f16a tcwg-llvmbot: Move arm7 globalisel bot back to normal
adds d3c1f8cf0 tcwg-llvmbot: Move arm7 globalisel bot back to normal
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 (dabf6f16a)
\
N -- N -- N refs/changes/36/44536/1 (d3c1f8cf0)
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/36/44336/2
in repository toolchain/jenkins-scripts.
discards bcbc89592 jenkins-helpers.sh (print_tester_label_for_target): Update label
adds ca0c712f4 jenkins-helpers.sh (print_tester_label_for_target): Update label
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 (bcbc89592)
\
N -- N -- N refs/changes/36/44336/2 (ca0c712f4)
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/36/44336/1
in repository toolchain/jenkins-scripts.
discards 8889d8c7d jenkins-helpers.sh (print_tester_label_for_target): Update label
adds a48865a2c jenkins-helpers.sh (print_tester_label_for_target): Update label
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 (8889d8c7d)
\
N -- N -- N refs/changes/36/44336/1 (a48865a2c)
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/36/43836/1
in repository toolchain/jenkins-scripts.
discards 70d350604 tcwg_bmk-build.sh: Fix results.regressions for bmk jobs
adds acc36dc15 tcwg_bmk-build.sh: Fix results.regressions for bmk jobs
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 (70d350604)
\
N -- N -- N refs/changes/36/43836/1 (acc36dc15)
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.