delta/buildstream.git/tests/elements, branch bschubert/python38 gitlab.com: buildstream/buildstream.git Reformat code using Black 2019-11-14T21:21:06+00:00 Chandan Singh csingh43@bloomberg.net 2019-11-11T17:07:09+00:00 122177153b14664a0e4fed85aa4f22b87cfabf56 As discussed over the mailing list, reformat code using Black. This is a one-off change to reformat all our codebase. Moving forward, we shouldn't expect such blanket reformats. Rather, we expect each change to already comply with the Black formatting style. 
As discussed over the mailing list, reformat code using Black. This is a
one-off change to reformat all our codebase. Moving forward, we
shouldn't expect such blanket reformats. Rather, we expect each change
to already comply with the Black formatting style.
setup.cfg: make xfail marks strict by default 2019-10-09T16:38:54+00:00 Darius Makovsky traveltissues@protonmail.com 2019-10-09T14:08:45+00:00 b7ab65e0ff6a11777b012450aa31c3d40fc05262 tests: remove strict kwargs from xfail marks 
tests: remove strict kwargs from xfail marks
tests/integration: Add test for filter element 2019-09-16T06:55:56+00:00 Thomas Coldrick thomas.coldrick@codethink.co.uk 2019-09-11T11:13:20+00:00 e019f2fb2236ba30b002166dc836cdfe57a3e937 Adds an integration test to check the `pass-integration` option for filter elements works. 
Adds an integration test to check the `pass-integration` option for
filter elements works.
element.py: Abstract not producing artifacts 2019-09-16T06:55:56+00:00 Thomas Coldrick thomas.coldrick@codethink.co.uk 2019-09-11T09:18:11+00:00 4e63710a5136c7ca8d87a5e86908e7de3de05f4a Currently the stack element does not produce an artifact, and sometimes has to be treated differently because of this. It is conceivable that someone will write a plugin that must be treated similarly and doesn't produce an artifact. As a result this commit abstracts this "not producing an artifact" feature of elements. 
Currently the stack element does not produce an artifact, and sometimes
has to be treated differently because of this. It is conceivable that
someone will write a plugin that must be treated similarly and doesn't
produce an artifact. As a result this commit abstracts this "not
producing an artifact" feature of elements.
filter.py: Fail if parent element is a stack 2019-09-16T06:55:56+00:00 Thomas Coldrick thomas.coldrick@codethink.co.uk 2019-09-10T10:14:45+00:00 b2af82add70ca6c582d08d916fb243493de397e2 As stack elements do not provide any artifacts, it is misleading to allow them as dependencies for filter elements. This commit makes a dependency on a stack element a failure with a descriptive error message. Additionally adds a test to make sure this works. Addresses #1104 
As stack elements do not provide any artifacts, it is misleading to
allow them as dependencies for filter elements. This commit makes a
dependency on a stack element a failure with a descriptive error
message.

Additionally adds a test to make sure this works.

Addresses #1104
filter.py: Allow passing integration commands 2019-09-16T06:55:56+00:00 Thomas Coldrick thomas.coldrick@codethink.co.uk 2019-09-10T09:53:17+00:00 8ff9262d9843a8e858a594c787ddbd156b4b3d3b It is tedious to manually copy the integration commands of the parent element into a filter element, so this allows it to be done automatically. Here we modify FilterElement.integrate() to allow us to pass through the parent's integration commands, iff an option is set. Also adds a test for the new feature, but this is not as comprehensive as would be idea, as getting to the integration commands which are run is a little more difficult. Addresses #1107 
It is tedious to manually copy the integration commands of the parent
element into a filter element, so this allows it to be done
automatically. Here we modify FilterElement.integrate() to allow us to
pass through the parent's integration commands, iff an option is set.

Also adds a test for the new feature, but this is not as comprehensive
as would be idea, as getting to the integration commands which are run
is a little more difficult.

Addresses #1107
Mark buildbox tests as xfail if they require non implemented features 2019-07-25T12:57:18+00:00 William Salmon will.salmon@codethink.co.uk 2019-07-19T09:16:03+00:00 91140a0360afb850aab529bd8375220d2e44c28f 






_yaml: Mark 'strip_node_info' as buildstream-private
2019-07-15T14:14:03+00:00

Benjamin Schubert
ben.c.schubert@gmail.com

2019-07-10T09:22:35+00:00

e6caca7071e9a007f0ec0b59662b7b28e05cd4b1












_yaml: Remove 'node_validate' and replace by 'MappingNode.validate_keys'
2019-07-15T14:14:03+00:00

Benjamin Schubert
ben.c.schubert@gmail.com

2019-07-03T17:01:30+00:00

8c9f41922ad16f8a031ac612bb35e493e8581380

- adapt all call sites to use the new API





- adapt all call sites to use the new API







tests: Change all calls to _yaml.dump to _yaml.rountrip_dump
2019-07-15T14:14:03+00:00

Benjamin Schubert
ben.c.schubert@gmail.com

2019-06-28T16:01:23+00:00

f7b461220ec2f1af3966ace12c21334f1f3b6457

Now that both are equivalent, we can skip the sanitization part before
the yaml call.





Now that both are equivalent, we can skip the sanitization part before
the yaml call.