[buildstream] branch juerg/cache-query updated (2787576 -> 177149d)

[ju...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

juergbi pushed a change to branch juerg/cache-query
in repository https://gitbox.apache.org/repos/asf/buildstream.git.


 discard 2787576  Call _initialize_state() in Element._new_from_load_element()
 discard bc4d6e6  Move artifact and source cache query trigger to Stream class
 discard 935eb82  element.py: Combine cache query and pull into `_load_artifact()`
 discard c0841ed  _elementsources.py: Make cache query explicit
 discard 59e64bd  _artifact.py: Make cache query explicit
 discard e90f3e9  _pipeline.py: Drop the optimization for cached elements in the planner
 discard 04bae10  fetchqueue.py: Don't skip elements with a cached failure
 discard 2b5a18a  tests/frontend/push.py: Allow pushing of dependencies
     add 13ac060  _messenger.py: Add a hook to explicitely start a new action context
     add a05e05a  job.py: Stop using the queue to send data between the child and parent
     add fa32cda  job.py: Completely remove the pipe between child and parent process
     add e429656  Merge pull request #1447 from apache/bschubert/remove-pipe-job
     add dc490ea  tests/frontend/push.py: Allow pushing of dependencies
     add 3a1ba18  fetchqueue.py: Don't skip elements with a cached failure
     add 6f47bd2  _pipeline.py: Drop the optimization for cached elements in the planner
     add 0efd0c0  _artifact.py: Make cache query explicit
     add c408501  _elementsources.py: Make cache query explicit
     add 73eaae8  element.py: Combine cache query and pull into `_load_artifact()`
     add 8110aaa  Use _load_artifact() for ArtifactElement
     add bc7a6cf  Move artifact and source cache query trigger to Stream class
     add 177149d  Call _initialize_state() in Element._new_from_load_element()

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   (2787576)
            \
             N -- N -- N   refs/heads/juerg/cache-query (177149d)

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/_artifactelement.py    |  18 +++--
 src/buildstream/_messenger.py          |  58 ++++++++++++----
 src/buildstream/_scheduler/jobs/job.py | 120 ++-------------------------------
 src/buildstream/_stream.py             |   7 +-
 src/buildstream/element.py             |  45 +++++++++----
 5 files changed, 98 insertions(+), 150 deletions(-)