This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/74/38174/2
in repository toolchain/jenkins-scripts.
discards 4a8c969f2 tcwg-report-stale-rr-jobs.sh: Add --human true/false option
adds eea781e7b tcwg-report-stale-rr-jobs.sh: Add --human true/false option
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 (4a8c969f2)
\
N -- N -- N refs/changes/74/38174/2 (eea781e7b)
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/74/38174/1
in repository toolchain/jenkins-scripts.
discards 691e8cb01 tcwg-report-stale-rr-jobs.sh: Add --human true/false option
new d54b4bc19 tcwg-report-stale-rr-jobs.sh: Add --human true/false option
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 (691e8cb01)
\
N -- N -- N refs/changes/74/38174/1 (d54b4bc19)
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/74/34874/2
in repository toolchain/jenkins-scripts.
discards 2382c087b Various shellcheck warning fixes
adds 8565f1816 Various shellcheck warning fixes
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 (2382c087b)
\
N -- N -- N refs/changes/74/34874/2 (8565f1816)
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/74/34874/1
in repository toolchain/jenkins-scripts.
discards 22eea483f Various shellcheck warning fixes
adds fd6552975 Various shellcheck warning fixes
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 (22eea483f)
\
N -- N -- N refs/changes/74/34874/1 (fd6552975)
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/74/34774/1
in repository toolchain/jenkins-scripts.
discards 7c6e7a67c tcwg-buildfarm.sh, start-container-docker.sh: Update default [...]
adds fc3949d81 tcwg-buildfarm.sh, start-container-docker.sh: Update default [...]
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 (7c6e7a67c)
\
N -- N -- N refs/changes/74/34774/1 (fc3949d81)
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/74/32874/2
in repository toolchain/jenkins-scripts.
discards 08db4ff5a tcwg_bmk-build.sh: Reboot boards before speed benchmarking
adds e22f981de tcwg_bmk-build.sh: Reboot boards before speed benchmarking
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 (08db4ff5a)
\
N -- N -- N refs/changes/74/32874/2 (e22f981de)
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/74/32874/1
in repository toolchain/jenkins-scripts.
discards 0a5321b91 tcwg_bmk-build.sh: Reboot boards before speed benchmarking
new 77966f01f tcwg_bmk-build.sh: Reboot boards before speed benchmarking
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 (0a5321b91)
\
N -- N -- N refs/changes/74/32874/1 (77966f01f)
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/74/32574/1
in repository toolchain/jenkins-scripts.
discards 4d87b608e Pass --disable-werror for profiled bootstraps.
adds c931223dd Pass --disable-werror for profiled bootstraps.
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 (4d87b608e)
\
N -- N -- N refs/changes/74/32574/1 (c931223dd)
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/74/30274/1
in repository toolchain/jenkins-scripts.
discards b5025b41a s/ubsan_bootstrap/bootstrap_ubsan and pass --enable bootstrap [...]
adds c9b2f0844 s/ubsan_bootstrap/bootstrap_ubsan and pass --enable bootstrap [...]
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 (b5025b41a)
\
N -- N -- N refs/changes/74/30274/1 (c9b2f0844)
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/74/30174/1
in repository toolchain/jenkins-scripts.
discards 3da806381 tcwg_kernel-bisect*: Use ==rr[mode] instead of --mode
adds 3551a2139 tcwg_kernel-bisect*: Use ==rr[mode] instead of --mode
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 (3da806381)
\
N -- N -- N refs/changes/74/30174/1 (3551a2139)
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.