This is an automated email from the ASF dual-hosted git repository.
tvb pushed a change to branch tristan/implement-retry-failed
in repository https://gitbox.apache.org/repos/asf/buildstream.git
omit 80f9e57b1 tests/integration/cachedfail.py: Test explicit retry of
failed builds
omit 22a057348 Implement --retry-failed option to the bst build command.
omit 08c93686d element.py: Fixup
omit a3da55c1f _messenger.py: Use datestampts instead of PID to
differentiate log files
new 33346bd87 _messenger.py: Use datestampts instead of PID to
differentiate log files
new 5a16a3366 Implement --retry-failed option to the bst build command.
new 729b263a0 tests/integration/cachedfail.py: Test explicit retry of
failed builds
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch 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 (80f9e57b1)
\
N -- N -- N refs/heads/tristan/implement-retry-failed (729b263a0)
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 "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
tests/integration/cachedfail.py | 1 -
1 file changed, 1 deletion(-)
