The algorithm adds elements to a dictionary and then sorts the dictionary
by the discovered depths while recursing - using an OrderedDict is enough
to ensure a stable order.

This fixes `bst show --deps plan ...` reporting different results on
each invocation.

This fixes an aspect of #824

Added a function to report the list of elements which appeared in
a given queue in the order of their first appearance.

For each sample project and expected result order, this test ensures that:

  * bst show --deps plan: Always shows the expected build order.

  * bst source fetch: Always executes in the expected build order.

  * bst build: Always builds in the expected order (disabled).

The build part of the test is currently disabled as the scheduler
seems to be messing with the order even in a `--builders 1` scenario.

Make build plan element list stable

See merge request !1058

Angelos Evripiotis authored Jan 11, 2019 and Angelos Evripiotis committed Jan 11, 2019

Bump the version of pytest-cov, so that we pick up the fix for
the '--no-cov' option breaking in pytest 4.0:

    https://github.com/pytest-dev/pytest-cov/pull/230

This was the error you would get prior to this version:

    _pytest.warning_types.RemovedInPytest4Warning: config.warn has been
    deprecated, use warnings.warn instead

Although it says 'deprecated', it did result in
termination with stack trace.

Angelos Evripiotis authored Jan 11, 2019 and Angelos Evripiotis committed Jan 11, 2019

To help new folks get to grips with pytest, add some tips on other
frequently used features.

pytest-cov==2.6.1, contributing: '--last-failed' and '--no-cov' tips

See merge request !1059

Minor correction, looks like we're not observing this queue
otherwise we'd be seeing crashes.

_scheduler/queues/queue.py: Put elements in the skip list, not jobs

See merge request !1063

.gitlab-ci.yml: Use latest freedesktop-sdk 18.08.25

Closes #858

See merge request !1064

During recent reorganizing of `.gitlab-ci.yml` to work with `tox`, seems
like we missed to update the image used by the overnight aarch tests,
meaning that they currently fail due to `tox` being missing from them.

While these tests will be skipped on MRs usually, here is an example of
what the tests look like if they are actually run with this change:
https://gitlab.com/BuildStream/buildstream/-/jobs/145449561.

Fixes #859.

Chandan/fix overnight aarch

Closes #859

See merge request !1065

Jürg Billeter authored Jan 10, 2019 and Tristan Van Berkom committed Jan 14, 2019

The path of the config file generated by testutils for completion tests
is passed as regular argument, not via COMP_WORDS. Use that config file
in complete_artifact() to ensure the test uses the right artifact
directory.

James Ennis authored Jan 09, 2019 and Tristan Van Berkom committed Jan 14, 2019

Since the artifact subcommand group has been created, we have been able
to tab complete both element names and artifact refs as arguments to
the artifact subcommands (e.g. bst artifact log), this commit adds a
test for this.

completions.py: Add a test for our artifact ref autocompletions

See merge request !1054

which include flatpak_repo plugin needed to build fdsdk

.gitlab-ci.yml: Use latest bst-external

Closes #861

See merge request !1068

This will help us check if BuildStream is working with the latest
version of dependencies, as per our constraints. This job is allowed to
fail but its failure should signal that we need to add stricter
constraints in some of our `.in` requirements files.

.gitlab-ci.yml: Add job to attempt to update dependencies

See merge request !1038

We already have tests for python 3.5 and 3.6 but not 3.7.

Fixes #838.

.gitlab-ci.yml: Add tests for python 3.7

Closes #838

See merge request !1074

Chandan Singh authored Jan 15, 2019 and Javier Jardón committed Jan 15, 2019

Starting from `pytest` version 4.1.0, `Node.get_marker()` has been
removed, and hence our tests break when running with newer versions of
`pytest`. It was deprecated since a while back but it has recently been
removed completely. Use `get_closest_marker()` as a replacement that is
suggested in the changelog, and seems to work fine for our use case.

See https://github.com/pytest-dev/pytest/pull/4564 for more context on
the upstream issue.

One way of verifying this change is that this should fix the recently
added `tests-fedora-update-deps` job, that was failing before due to
this issue.

conftest.py: Don't use deprecated get_marker() function

See merge request !1073

Found during #833.

`git rev-list --boundary tag..HEAD` unfortunately gives boundaries
that are deeper than should when there is a merge commit between `tag`
and `HEAD`. The common ancestory of the two parents of the merge is
a boundary instead of the parent of the branch that is not traversed.

`--ancestry-path` fixes this issue by restricting `git` traversing
those branches.

`git rev-list --boundary HEAD..HEAD` does not return any boundary.
So in this case we need to manually tag the HEAD as a boundary.

buildstream/_gitsourcebase.py: Reduce git history for git describe.

See merge request !1069

Small documentation/comment fixes in context.py

See merge request !1072

Other components will start to reply on cas modules, and not the artifact cache
modules so it should be organized to reflect this.

All relevant imports have been changed.

Part #802

Part of #802

List of methods moved
* Initialization check: made it a class method that is run in a subprocess, for
  when checking in the main buildstream process.
* fetch_blobs
* send_blobs
* verify_digest_on_remote
* push_method

Part of #802

Cas refactor

See merge request !1071

A plugin's deprecation warning may be silenced by a project by adding
the plugin to the list 'supress-deprecation-warnings' in the project's
project.conf