Note that the ProvenanceFile's names will be incorrect after loading
from the cache, but this is currently only used for writeback, which
isn't used in junctions.

Lachlan authored Oct 05, 2018 and Jonathan Maw committed Oct 15, 2018

* Fix to CWD issue provided by Jonathan Maw

Lachlan authored Oct 12, 2018 and Jonathan Maw committed Oct 15, 2018

* Test in same style as test_yamlcache_used
* Move of project not required so removed

Add YAM cache testing to yaml tests and further YAML cache refinements

See merge request !836

William Salmon authored Sep 13, 2018 and Phil Dawson committed Oct 16, 2018

The code was creating the cwd folder but when the workspace was
mounted in to the buildroot it was hiding the folder created in it
behind the bind mounted workspace.

However by using the bubblewarp `--dir` directive to ensure that cwd
exists we can cover both workspace and non workspace situations with
the same method.

For issue #512 in Gitlab.

William Salmon authored Sep 14, 2018 and Phil Dawson committed Oct 16, 2018

Build stream was only creating command-subdir for non workspace builds
this has now been fixed, and this regression test should support the
feature.

For issue #512 in Gitlab.

William Salmon authored Sep 10, 2018 and Phil Dawson committed Oct 16, 2018

Adding the conf-root variable makes creating out of source builds
slightly easier.

For issue #512 in Gitlab.

William Salmon authored Oct 10, 2018 and Phil Dawson committed Oct 16, 2018

For issue #512 in Gitlab.

William Salmon authored Sep 11, 2018 and Phil Dawson committed Oct 16, 2018

For issue #512 in Gitlab.

William Salmon authored Oct 04, 2018 and Phil Dawson committed Oct 16, 2018

For issue #512 in Gitlab.

Out of source builds

Closes #512

See merge request !776

We shouldn't need it to persist now that we cache failed build dirs.

This change breaks the test
`tests/integration/shell.py::test_sysroot_workspace_visible`.
I can no longer see a use-case for this test.
AIUI, it tested that the failed build sysroot stored in the builddir has
the workspace's files in, despite the workspace being unmounted.
I believe this behaviour is made redundant by cached buildtrees.

This fixes part of #539

This includes changes in app.py:
* Interactive failure shell no longer uses the failed build sysroot,
  defaulting to the cached build tree.
* Always allow producing a failure shell.

Changes in element.py are:
* Errors caused by building don't store the failed build sysroot.
* When staging sources, will stage the element's cached build tree if it
  exists.

This fixes part of #539

This is related to #539

i.e. instead of taking a directory that must contain "root" and
"scratch", and treating "root" as the root, use the directory directly.

In element.py:
* __sandbox takes the `bare_sandbox` arg, to pass into the sandbox's constructor

In sandbox.py:
* If bare_sandbox, `_root` is the passed-in directory, and `__scratch`
  is None.
* Trying to use `__scratch` when bare_sandbox is True is a bug.

In _mount.py:
* Don't get the value of `__scratch` if it's not needed.

This is part of #539

This is related to #539