This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/71/45771/1
in repository toolchain/jenkins-scripts.
discards fb59e1444 Revert "tcwg-update-llvmbot-containers.sh: Add silent flang l [...]
adds 436370bc1 Revert "tcwg-update-llvmbot-containers.sh: Add silent flang l [...]
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 (fb59e1444)
\
N -- N -- N refs/changes/71/45771/1 (436370bc1)
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/71/45671/1
in repository toolchain/jenkins-scripts.
discards 71a58f4d3 round-robin-notify.sh (bmk_generate_extra_details): Fix
adds 45f0e414c round-robin-notify.sh (bmk_generate_extra_details): Fix
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 (71a58f4d3)
\
N -- N -- N refs/changes/71/45671/1 (45f0e414c)
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/71/45571/2
in repository toolchain/jenkins-scripts.
discards 5e1b7b44a round-robin.sh (reset_artifacts): Split base-artifacts.git repo
adds 7cdcc8f28 round-robin.sh (reset_artifacts): Split base-artifacts.git repo
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 (5e1b7b44a)
\
N -- N -- N refs/changes/71/45571/2 (7cdcc8f28)
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/71/45571/1
in repository toolchain/jenkins-scripts.
discards 456369d54 round-robin.sh (reset_artifacts): Split base-artifacts.git repo
adds 98d4ce5bd round-robin.sh (reset_artifacts): Split base-artifacts.git repo
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 (456369d54)
\
N -- N -- N refs/changes/71/45571/1 (98d4ce5bd)
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/71/45471/1
in repository toolchain/jenkins-scripts.
discards b74e95900 tcwg_bmk-build.sh: Add --weight option to samples-variability.py
adds 24e7491b4 tcwg_bmk-build.sh: Add --weight option to samples-variability.py
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 (b74e95900)
\
N -- N -- N refs/changes/71/45471/1 (24e7491b4)
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/71/44971/2
in repository toolchain/jenkins-scripts.
discards 5a317b846 Pass --security instead of --docker_opts to start-container-d [...]
adds 9e655a59b Pass --security instead of --docker_opts to start-container-d [...]
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 (5a317b846)
\
N -- N -- N refs/changes/71/44971/2 (9e655a59b)
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/71/44971/1
in repository toolchain/jenkins-scripts.
discards c2a3da4c4 Pass --privilged instead of --docker_opts to start-container- [...]
new 72ea885bc Pass --privilged instead of --docker_opts to start-container- [...]
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 (c2a3da4c4)
\
N -- N -- N refs/changes/71/44971/1 (72ea885bc)
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/71/44571/2
in repository toolchain/jenkins-scripts.
discards 204883126 start-container-docker.sh: Replace --docket_opts/--default_se [...]
adds c9df63ab6 start-container-docker.sh: Replace --docket_opts/--default_se [...]
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 (204883126)
\
N -- N -- N refs/changes/71/44571/2 (c9df63ab6)
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/71/44571/1
in repository toolchain/jenkins-scripts.
discards e860d725b start-container-docker.sh: Replace --docket_opts/--default_se [...]
new 1e5332c6c start-container-docker.sh: Replace --docket_opts/--default_se [...]
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 (e860d725b)
\
N -- N -- N refs/changes/71/44571/1 (1e5332c6c)
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/71/43671/3
in repository toolchain/jenkins-scripts.
discards 1fe97d0c1 round-robin.sh,round-robin-notify.sh,dashboard-generate-squad [...]
adds a8faabf7c round-robin.sh,round-robin-notify.sh,dashboard-generate-squad [...]
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 (1fe97d0c1)
\
N -- N -- N refs/changes/71/43671/3 (a8faabf7c)
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.