This is required because if there are projects with the same name
loaded, that have elements in the same path, with the same contents,
they are considered the same, despite actually belonging to different
Projects.

This fixes buildstream issue #795

James Ennis authored Nov 30, 2018 and Jonathan Maw committed Dec 03, 2018

Test required to close #795 - We should be able to build a project which refers
to the same junction twice, but with two different filenames.

_yamlcache.py: Use a project's junction name if present

Closes #795

See merge request !980

Commit 3fa79d8d, part of an initiative for caching of the failed builds,
introduced a call to Element._update_state() after a job completes and before
entering the error handling harness intended for handling plugin raised errors.

Element._update_state() can result in triggering plugin code to
run, so this is incorrect, and causes raised errors to crash BuildStream
if they happen here.

After analyzing the code, it appears that this additional call to
Element._update_state() is unneeded, and was only added because the
state needs to be updated for a failure as well as a success.

Instead, we now have the BuildQueue call Element._assemble_done()
unconditionally, regardless of whether the build was successful
or not, which has the same effect and also reads better.

In addition, added a FIXME comment that we are still conditionally
updating the artifact cache size from BuildQueue.done() only
if the build is successful, which is incorrect because failed builds
also increase the local artifact cache size - to fix this we need
to communicate the added artifact size through Element._assemble()
regardless of whether the build succeeded or failed.

_scheduler/queues/queue.py: Don't call update state outside of error handling harness

See merge request !988

Instead of tag information being fetched which can change with time,
they are tracked and saved in the projects.refs/.bst. Then we re-tag
automatically the closest tag so that `git describe` works and is
reproducible.

This new feature is opt-in with the new `track-tags` configuration,
and must be used to fix modules which are broken by our new policy
of omitting the `.git/` repository when staging git sources.

This fixes issue #487

Track of git tags and save them to reproduce minimum shallow repository

Closes #487

See merge request !906

In element, platform asks for host os and architecture to default to when
SandboxConfig is initialised.
This changes element cache keys so those have been updated in the tests.

Also update tests to be consistent with this

These are contained within the platform field.

Same format as OptionArch tests, but with OS's.

  o _platform/linux.py: Add linux32 flag to send to sandbox bwrap when the
    build arch is x86-32 and the machines arch is x86-64 or similarly with
    aarch32 and aarch64.
  o sandbox/_sandboxbwrap.py: Use flag passed to start bwrap command with
    linux32 if set.

Execution environment reqs

Closes #775

See merge request !969

Get cascache.py to use this

Stops unneccesary pushing of builds that have already been built, just checks
the action cache to begin with.

Fixes #628

The endpoint may not necessarily be the same as execution-service endpoint.

Part of #628

Part of #628

Remote-execution client flow optimisation

Closes #628

See merge request !982

Instead of duplicating the whole test body, run it twice while
checking for a warning or an error depending on the parameter.

This also ensures it is exposed via the main buildstream __init__.py
file, fixes the imports of CoreWarnings, and adjusts the documentation
links to point to the right place.

Now the commands have documentation linkability so we can link to
them when referring to them anywhere in the docs. This reference
was previously referring to a bogus non-existent `build-stream track`,
maybe this dates way back to the days before we named the frontend `bst`.

Fixes the configurable warning part of this to properly link
to the project.conf documentation describing what configurable
warnings actually are.

Also fix the plugin raise the actual configurable warning which
it advertizes that it raises; which is 'inconsistent-submodule',
not 'inconsistent-submodules'.

Change 'INCONSISTENT_SUBMODULE' for 'WARN_INCONSISTENT_SUBMODULE' to
make things a bit more readable and comprehensive.

Misc cleanups

See merge request !993

_frontend/cli.py: Added helper function for walking through dirs to return files

data/projectconfig.yaml: Added new variable for `default: target-element`

_project.py: Added config variable to node_validate

Added --world flag to list of expected flags

Added test files to be built using build --world