This is an automated email from the git hooks/post-receive script.
maxim.kuvyrkov pushed a change to reference refs/changes/45/43745/4
in repository toolchain/jenkins-scripts.
discards 4d8bb39e2 round-robin.sh (build_abe): Re-run testsuites until convergence
adds bdef6ffc5 round-robin.sh (build_abe): Re-run testsuites until convergence
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 (4d8bb39e2)
\
N -- N -- N refs/changes/45/43745/4 (bdef6ffc5)
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/45/43745/3
in repository toolchain/jenkins-scripts.
discards c505812ee round-robin.sh (build_abe): Re-run testsuites until convergence
adds d04d732ca round-robin.sh (build_abe): Re-run testsuites until convergence
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 (c505812ee)
\
N -- N -- N refs/changes/45/43745/3 (d04d732ca)
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/45/43745/2
in repository toolchain/jenkins-scripts.
discards 0d48687ec round-robin.sh (build_abe): Re-run testsuites until convergence
adds 1b09370c5 round-robin.sh (build_abe): Re-run testsuites until convergence
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 (0d48687ec)
\
N -- N -- N refs/changes/45/43745/2 (1b09370c5)
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/45/43745/1
in repository toolchain/jenkins-scripts.
discards b48697082 round-robin.sh (build_abe): Re-run testsuites until convergence
new ca503dbe7 round-robin.sh (build_abe): Re-run testsuites until convergence
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 (b48697082)
\
N -- N -- N refs/changes/45/43745/1 (ca503dbe7)
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/45/43645/2
in repository toolchain/jenkins-scripts.
discards 38da4bf34 round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...]
adds a76f8ce98 round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...]
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 (38da4bf34)
\
N -- N -- N refs/changes/45/43645/2 (a76f8ce98)
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/45/43645/1
in repository toolchain/jenkins-scripts.
discards b41d36b4d round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...]
new 86fe6807b round-robin.sh,round-robin-notify.sh,tcwg_bmk-build.sh: rewor [...]
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 (b41d36b4d)
\
N -- N -- N refs/changes/45/43645/1 (86fe6807b)
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/45/43545/1
in repository toolchain/jenkins-scripts.
discards 8b0e9c4a5 round-robin.sh (reset_artifacts): Don't propagate git data
adds 42c962ca8 round-robin.sh (reset_artifacts): Don't propagate git data
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 (8b0e9c4a5)
\
N -- N -- N refs/changes/45/43545/1 (42c962ca8)
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/45/43145/2
in repository toolchain/jenkins-scripts.
discards d4bf7de19 tcwg_gnu-build.sh: Remove gdb.server/unittest.exp from stable [...]
adds 50f896ac7 tcwg_gnu-build.sh: Remove gdb.server/unittest.exp from stable [...]
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 (d4bf7de19)
\
N -- N -- N refs/changes/45/43145/2 (50f896ac7)
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/45/43145/1
in repository toolchain/jenkins-scripts.
discards 9a3ec824d tcwg_gnu-build.sh: Remove gdb.server/unittest.exp from stable [...]
adds 5804d9273 tcwg_gnu-build.sh: Remove gdb.server/unittest.exp from stable [...]
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 (9a3ec824d)
\
N -- N -- N refs/changes/45/43145/1 (5804d9273)
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/45/42345/3
in repository toolchain/jenkins-scripts.
discards 2326b6422 Use compare-results.py instead of csvs2table.py.
new ea72a87ae Use compare-results.py instead of csvs2table.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 (2326b6422)
\
N -- N -- N refs/changes/45/42345/3 (ea72a87ae)
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.