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 16540c66e man: Updated man pages after adding --retry-failed
omit 07622fec8 tests/integration/cachedfail.py: Test explicit retry of
failed builds
omit 684e9856e Implement --retry-failed option to the bst build command.
add 78cb6be83 Implement --retry-failed option to the bst build command.
add 7a4383b90 tests/integration/cachedfail.py: Test explicit retry of
failed builds
add 79027138b man: Updated man pages after adding --retry-failed
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 (16540c66e)
\
N -- N -- N refs/heads/tristan/implement-retry-failed (79027138b)
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.
No new revisions were added by this update.
Summary of changes:
src/buildstream/element.py | 22 +++++++++-------------
1 file changed, 9 insertions(+), 13 deletions(-)
