This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/33/42333/1
in repository toolchain/jenkins-scripts.
discards cb9d1e157 dashboard-push-one-branch.sh: Recreate first csv results if n [...]
adds 291352db2 dashboard-push-one-branch.sh: Recreate first csv results if n [...]
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 (cb9d1e157)
\
N -- N -- N refs/changes/33/42333/1 (291352db2)
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/33/42133/5
in repository toolchain/jenkins-scripts.
discards c96e6e9e5 jenkins-helpers.sh (run_step): Support changing environment
adds 7558920be jenkins-helpers.sh (run_step): Support changing environment
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 (c96e6e9e5)
\
N -- N -- N refs/changes/33/42133/5 (7558920be)
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/33/42133/4
in repository toolchain/jenkins-scripts.
discards 88d45066f jenkins-helpers.sh (run_step): Support changing environment
adds 356c76ea1 jenkins-helpers.sh (run_step): Support changing environment
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 (88d45066f)
\
N -- N -- N refs/changes/33/42133/4 (356c76ea1)
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/33/42133/3
in repository toolchain/jenkins-scripts.
discards 3b358c2bd jenkins-helpers.sh (run_step): Support changing environment
adds 9065fab03 jenkins-helpers.sh (run_step): Support changing environment
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 (3b358c2bd)
\
N -- N -- N refs/changes/33/42133/3 (9065fab03)
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/33/42133/2
in repository toolchain/jenkins-scripts.
discards 7ea98d5e0 jenkins-helpers.sh (run_step): Support changing environment
new 0476709ac jenkins-helpers.sh (run_step): Support changing environment
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 (7ea98d5e0)
\
N -- N -- N refs/changes/33/42133/2 (0476709ac)
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/33/42133/1
in repository toolchain/jenkins-scripts.
discards 5928ae397 jenkins-helpers.sh (run_step): Support changing environment
new ffffca6ff jenkins-helpers.sh (run_step): Support changing environment
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 (5928ae397)
\
N -- N -- N refs/changes/33/42133/1 (ffffca6ff)
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/33/42033/2
in repository toolchain/jenkins-scripts.
discards e52161e1f round-robin-bisect.sh: Check all available interesing commits
discards ef11d493b round-robin-bisect.sh: Cleanup code to try interesting-commits
discards e20e5a5fc round-robin.sh, dashboard-generate-squad.sh: Handle errors dr [...]
adds d8389d726 round-robin.sh, dashboard-generate-squad.sh: Handle errors dr [...]
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 (e52161e1f)
\
N -- N -- N refs/changes/33/42033/2 (d8389d726)
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 | 634 --------------------------------------------------
round-robin-notify.sh | 224 ------------------
2 files changed, 858 deletions(-)
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/33/42033/1
in repository toolchain/jenkins-scripts.
discards b03a40aa5 round-robin-bisect.sh: Check all available interesing commits
discards 1bb4b3e81 round-robin-bisect.sh: Cleanup code to try interesting-commits
discards 5aeaee2f3 start-container-docker.sh: Switch lts_1 to Ubuntu 20.04 Focal
adds 773b4f59d start-container-docker.sh: Switch lts_1 to Ubuntu 20.04 Focal
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 (b03a40aa5)
\
N -- N -- N refs/changes/33/42033/1 (773b4f59d)
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 | 634 --------------------------------------------------
round-robin-notify.sh | 224 ------------------
2 files changed, 858 deletions(-)
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/33/41833/1
in repository toolchain/jenkins-scripts.
discards 5081fcfa6 round-robin.sh: Fix baseline builds during bisect
adds 5900926d1 round-robin.sh: Fix baseline builds during bisect
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 (5081fcfa6)
\
N -- N -- N refs/changes/33/41833/1 (5900926d1)
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/33/41433/1
in repository toolchain/jenkins-scripts.
discards 8df30de96 round-robin-bisect.sh: Be cautious about spamming upstream de [...]
discards 2629d23d1 tcwg-benchmark.sh: Don't start host containers on machines
adds 05f054ba3 tcwg-benchmark.sh: Don't start host containers on machines
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 (8df30de96)
\
N -- N -- N refs/changes/33/41433/1 (05f054ba3)
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 | 867 --------------------------------------------------
1 file changed, 867 deletions(-)
delete mode 100755 round-robin-bisect.sh
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.