This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/63/39163/3
in repository toolchain/jenkins-scripts.
discards 8fc222328 round-robin-bisect.sh: Update email preferences
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 (8fc222328)
\
N -- N -- N refs/changes/63/39163/3 (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:
round-robin-bisect.sh | 761 --------------------------------------------------
1 file changed, 761 deletions(-)
delete mode 100755 round-robin-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/63/39163/2
in repository toolchain/jenkins-scripts.
discards a8662a237 round-robin-bisect.sh: Update email preferences
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 (a8662a237)
\
N -- N -- N refs/changes/63/39163/2 (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:
round-robin-bisect.sh | 761 --------------------------------------------------
1 file changed, 761 deletions(-)
delete mode 100755 round-robin-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/63/39163/1
in repository toolchain/jenkins-scripts.
discards 2454f1089 round-robin-bisect.sh: Update email preferences
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 (2454f1089)
\
N -- N -- N refs/changes/63/39163/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:
round-robin-bisect.sh | 760 --------------------------------------------------
1 file changed, 760 deletions(-)
delete mode 100755 round-robin-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/63/37863/2
in repository toolchain/jenkins-scripts.
discards fe08cf7ec tcwg-update-llvmbot-containers.sh: Add buildkite bot for AArc [...]
adds 69534c64a tcwg-update-llvmbot-containers.sh: Add buildkite bot for AArc [...]
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 (fe08cf7ec)
\
N -- N -- N refs/changes/63/37863/2 (69534c64a)
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/63/37863/1
in repository toolchain/jenkins-scripts.
discards 14bba33d9 tcwg-update-llvmbot-containers.sh: Support buildkite bots for libcxx
new 65c3931c2 tcwg-update-llvmbot-containers.sh: Support buildkite bots for libcxx
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 (14bba33d9)
\
N -- N -- N refs/changes/63/37863/1 (65c3931c2)
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/63/37763/1
in repository toolchain/jenkins-scripts.
discards 153500e2b round-robin-bisect.sh: Go through interesting-commit in forwa [...]
discards d78931dd8 round-robin-bisect.sh: Fix exiting a subshell
discards 80aac341b round-robin-bisect.sh: Update Jira card for GNU CI
discards 54205da2f round-robin-bisect.sh: Update jira card numbers for reports
discards 246749d4b tcwg_bmk-build.sh: Fix unbound variable error
adds 640034e7f tcwg_bmk-build.sh: Fix unbound variable error
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 (153500e2b)
\
N -- N -- N refs/changes/63/37763/1 (640034e7f)
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-bisect.sh | 721 --------------------------------------------------
1 file changed, 721 deletions(-)
delete mode 100755 round-robin-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/63/36363/1
in repository toolchain/jenkins-scripts.
discards 05627cada tcwg-benchmark.sh: Prepare board for benchmarking before star [...]
adds 66b1d2182 tcwg-benchmark.sh: Prepare board for benchmarking before star [...]
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 (05627cada)
\
N -- N -- N refs/changes/63/36363/1 (66b1d2182)
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/63/34663/3
in repository toolchain/jenkins-scripts.
discards 086bec00a docker-run.sh: Use the correct run/cleanup functions when --p [...]
adds 0788d0f7d docker-run.sh: Use the correct run/cleanup functions when --p [...]
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 (086bec00a)
\
N -- N -- N refs/changes/63/34663/3 (0788d0f7d)
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/63/34663/2
in repository toolchain/jenkins-scripts.
discards 4e5da02df docker-run.sh: Use the correct run/cleanup functions when --p [...]
new f5d31caf1 docker-run.sh: Use the correct run/cleanup functions when --p [...]
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 (4e5da02df)
\
N -- N -- N refs/changes/63/34663/2 (f5d31caf1)
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/63/34663/1
in repository toolchain/jenkins-scripts.
discards c7fb531be docker-run.sh: Use the correct run/cleanup functions when --p [...]
new 72cc1e088 docker-run.sh: Use the correct run/cleanup functions when --p [...]
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 (c7fb531be)
\
N -- N -- N refs/changes/63/34663/1 (72cc1e088)
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.