This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/57/39257/2
in repository toolchain/jenkins-scripts.
discards 0e7fa7714 [NFC] round-robin.sh: Cleanup reset_artifacts()
adds 019a44fb0 [NFC] round-robin.sh: Cleanup reset_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 (0e7fa7714)
\
N -- N -- N refs/changes/57/39257/2 (019a44fb0)
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/39257/1
in repository toolchain/jenkins-scripts.
discards e30a94de5 [NFC] round-robin.sh: Cleanup reset_artifacts()
adds 93ffead39 [NFC] round-robin.sh: Cleanup reset_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 (e30a94de5)
\
N -- N -- N refs/changes/57/39257/1 (93ffead39)
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/39157/1
in repository toolchain/jenkins-scripts.
discards 8c7e4defb tcwg_gnu-build.sh: Fix broken pipe from "head"
adds 6ec5601d2 tcwg_gnu-build.sh: Fix broken pipe from "head"
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 (8c7e4defb)
\
N -- N -- N refs/changes/57/39157/1 (6ec5601d2)
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/36557/1
in repository toolchain/jenkins-scripts.
discards 88c6534f9 tcwg-update-llvmbot-containers: Add a buildbot
adds 7c134b3eb tcwg-update-llvmbot-containers: Add a buildbot
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 (88c6534f9)
\
N -- N -- N refs/changes/57/36557/1 (7c134b3eb)
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/35857/2
in repository toolchain/jenkins-scripts.
discards 995b537d9 tcwg_bmk-build.sh: Gracefully handle benchmarking board going [...]
adds db95d5f67 tcwg_bmk-build.sh: Gracefully handle benchmarking board going [...]
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 (995b537d9)
\
N -- N -- N refs/changes/57/35857/2 (db95d5f67)
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/35857/1
in repository toolchain/jenkins-scripts.
discards 53dde908e tcwg_bmk-build.sh: Gracefully handle benchmarking board going [...]
adds 8953477b4 tcwg_bmk-build.sh: Gracefully handle benchmarking board going [...]
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 (53dde908e)
\
N -- N -- N refs/changes/57/35857/1 (8953477b4)
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/32657/1
in repository toolchain/jenkins-scripts.
discards 91baa4479 jenkins-helpers.sh: Fix print_bind_mounts()
adds 3d020aa72 jenkins-helpers.sh: Fix print_bind_mounts()
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 (91baa4479)
\
N -- N -- N refs/changes/57/32657/1 (3d020aa72)
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/30357/1
in repository toolchain/jenkins-scripts.
discards c987b21dd Revert "tcwg_bmk-build: Use $reset_baseline instead of $rr[re [...]
adds f08328267 Revert "tcwg_bmk-build: Use $reset_baseline instead of $rr[re [...]
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 (c987b21dd)
\
N -- N -- N refs/changes/57/30357/1 (f08328267)
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/30257/3
in repository toolchain/jenkins-scripts.
discards 5cbc7baf0 tcwg_kernel-bisect.sh: Detect linker and make errors in the logs
discards e7b992985 tcwg_kernel-bisect.sh: Use rr[ci_config] instead of its sub-items
discards 21cb97b04 Set run_step_status to 0 before running step.
adds 6be79ada6 Set run_step_status to 0 before running step.
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 (5cbc7baf0)
\
N -- N -- N refs/changes/57/30257/3 (6be79ada6)
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:
tcwg_kernel-bisect.sh | 364 --------------------------------------------------
1 file changed, 364 deletions(-)
delete mode 100755 tcwg_kernel-bisect.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/30257/2
in repository toolchain/jenkins-scripts.
discards 02fcf2037 tcwg_kernel-bisect.sh: Detect linker and make errors in the logs
discards 661866405 tcwg_kernel-bisect.sh: Use rr[ci_config] instead of its sub-items
discards 99300555a jenkins-helpers.sh: Workaround DNS issue
adds 06af2d36b jenkins-helpers.sh: Workaround DNS issue
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 (02fcf2037)
\
N -- N -- N refs/changes/57/30257/2 (06af2d36b)
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:
tcwg_kernel-bisect.sh | 364 --------------------------------------------------
1 file changed, 364 deletions(-)
delete mode 100755 tcwg_kernel-bisect.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.