This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/14/33014/1
in repository toolchain/jenkins-scripts.
discards 36cac81c9 round-robin-bisect.sh: Add more links to jira regression comments
discards 3d6ec47b2 round-robin-bisect.sh: Fix minor bugs around string processing
discards 2dc4fca2b jenkins-helpers.sh: Add a timeout for "ssh $board true" in wa [...]
adds ea22993d8 jenkins-helpers.sh: Add a timeout for "ssh $board true" in wa [...]
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 (36cac81c9)
\
N -- N -- N refs/changes/14/33014/1 (ea22993d8)
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 | 574 --------------------------------------------------
1 file changed, 574 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/14/32814/2
in repository toolchain/jenkins-scripts.
discards 8276cc460 tcwg_bmk-build.sh: Slightly change path of bmk results on bkp [...]
adds 8c1768ef6 tcwg_bmk-build.sh: Slightly change path of bmk results on bkp [...]
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 (8276cc460)
\
N -- N -- N refs/changes/14/32814/2 (8c1768ef6)
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/14/32814/1
in repository toolchain/jenkins-scripts.
discards 3ea485ed1 tcwg_bmk-build.sh: Slightly change path of bmk results on bkp [...]
new 0f46624db tcwg_bmk-build.sh: Slightly change path of bmk results on bkp [...]
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 (3ea485ed1)
\
N -- N -- N refs/changes/14/32814/1 (0f46624db)
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/14/31014/4
in repository toolchain/jenkins-scripts.
discards 59d832057 jenkins-helpers.sh: Improve handling of git errors in run_wit [...]
adds a25ce5d15 jenkins-helpers.sh: Improve handling of git errors in run_wit [...]
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 (59d832057)
\
N -- N -- N refs/changes/14/31014/4 (a25ce5d15)
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/14/31014/3
in repository toolchain/jenkins-scripts.
discards 91b194ca1 jenkins-helpers.sh: Improve handling of git errors in run_wit [...]
new f4c22db24 jenkins-helpers.sh: Improve handling of git errors in run_wit [...]
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 (91b194ca1)
\
N -- N -- N refs/changes/14/31014/3 (f4c22db24)
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/14/31014/2
in repository toolchain/jenkins-scripts.
discards ed055b207 jenkins-helpers.sh: Improve handling of git errors in run_wit [...]
new eb1668303 jenkins-helpers.sh: Improve handling of git errors in run_wit [...]
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 (ed055b207)
\
N -- N -- N refs/changes/14/31014/2 (eb1668303)
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/14/31014/1
in repository toolchain/jenkins-scripts.
discards 9b2749ec4 jenkins-helpers.sh: Improve handling of git errors in run_wit [...]
adds c1be79aca jenkins-helpers.sh: Improve handling of git errors in run_wit [...]
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 (9b2749ec4)
\
N -- N -- N refs/changes/14/31014/1 (c1be79aca)
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/14/30114/1
in repository toolchain/jenkins-scripts.
discards 043690cf1 tcwg_bmk-build: Use $reset_baseline instead of $rr[reset_baseline]
adds 95c1cbfcc tcwg_bmk-build: Use $reset_baseline instead of $rr[reset_baseline]
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 (043690cf1)
\
N -- N -- N refs/changes/14/30114/1 (95c1cbfcc)
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/14/29914/1
in repository toolchain/jenkins-scripts.
discards 6998c3b88 [WIP] tcwg_bmk project
new bd312ffce [WIP] tcwg_bmk project
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 (6998c3b88)
\
N -- N -- N refs/changes/14/29914/1 (bd312ffce)
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/13/46213/8
in repository toolchain/jenkins-scripts.
discards 8c2c05d0b round-robin-notify.sh (print_mail_body): Move Jira link higher
discards 93c3a47c8 generate-cimonitor-dashboard.py: Add status.csv info if exist
adds 1883ff8f9 generate-cimonitor-dashboard.py: Add status.csv info if exist
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 (8c2c05d0b)
\
N -- N -- N refs/changes/13/46213/8 (1883ff8f9)
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-baseline.sh | 567 -------------
round-robin-bisect.sh | 681 ----------------
round-robin-notify.sh | 2076 -----------------------------------------------
3 files changed, 3324 deletions(-)
delete mode 100755 round-robin-baseline.sh
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.