delta/buildstream.git/tests/sources, branch external_plugin_errors gitlab.com: buildstream/buildstream.git Updated test cases for internal API changes stemming from project options 2017-10-10T10:29:59+00:00 Tristan Van Berkom tristan.vanberkom@codethink.co.uk 2017-10-04T08:39:07+00:00 fa512fef4765cc63ceeb4a901a3a517cb83606d6 






Updating test cases to construct the project/loader properly again.
2017-10-08T08:03:36+00:00

Tristan Van Berkom
tristan.vanberkom@codethink.co.uk

2017-09-22T03:16:45+00:00

bc8a2ebb3b0d8e0f535b2956b9c6a3ad0a05fcef

This had changed when we added project variants and had to split
up the loading steps a bit, now all is back to normal without variants.





This had changed when we added project variants and had to split
up the loading steps a bit, now all is back to normal without variants.







Fix affected test cases
2017-09-14T10:05:21+00:00

Tristan Maat
tristan.maat@codethink.co.uk

2017-09-07T13:59:23+00:00

6bb468a00d76896a0a4da1e5e02bd9c0023ff954












tar.py source test case: Stop using tar's private _sha256sum() method
2017-09-12T15:38:02+00:00

Tristan Van Berkom
tristan.vanberkom@codethink.co.uk

2017-09-12T15:38:02+00:00

5b995dd1543b9476abfe6f1d42dc43cd5d0ea7dc

That was removed anyway, now use utils.sha256sum() to calculate
the expected tar ref.





That was removed anyway, now use utils.sha256sum() to calculate
the expected tar ref.







Add patch source plugin
2017-09-09T19:58:51+00:00

Chandan Singh
csingh43@bloomberg.net

2017-08-24T20:07:15+00:00

b1b5cd56386272b04487eb7563198215ce9ae9a1

Fixes #63





Fixes #63







tests/sources/ostree.py: Removed test and data.
2017-09-04T16:03:12+00:00

Tristan Van Berkom
tristan.vanberkom@codethink.co.uk

2017-09-04T16:03:12+00:00

ce675ba46b6745b2625fc21e03a8fbf50b2de78b

This was testing nothing whatsoever about the behavior
of the plugin but just running for the sake of running.

Removing this does not effect the coverage report of
the ostree.py plugin.





This was testing nothing whatsoever about the behavior
of the plugin but just running for the sake of running.

Removing this does not effect the coverage report of
the ostree.py plugin.







tests/source/git.py: Skip if git is not available
2017-09-04T15:48:44+00:00

Tristan Van Berkom
tristan.vanberkom@codethink.co.uk

2017-09-04T15:47:22+00:00

22995779bc407712f82de20a2f2d867700f6c281












tests/sources/bzr.py: Use site.py to determine presence of bzr
2017-09-04T15:48:44+00:00

Tristan Van Berkom
tristan.vanberkom@codethink.co.uk

2017-09-04T15:46:29+00:00

38ec46bb51d7863ac1e8eaf5dffce2a530cb70ac












tests/sources/ostree.py: Removed http server test
2017-09-04T06:25:14+00:00

Tristan Van Berkom
tristan.vanberkom@codethink.co.uk

2017-09-04T00:25:42+00:00

f121ed38ad43b8c8ca8759e6e82d6f60d4a4431b

This was failing intermittently if the test suite is
run multiple times (as it takes some time for the port 8000
to become available again).

Further, this test case was immaterial and not testing
any ostree functionality whatsoever. Presumably this was
a remnant from a time when the test case attempts to fetch
the payload over a local http connection.





This was failing intermittently if the test suite is
run multiple times (as it takes some time for the port 8000
to become available again).

Further, this test case was immaterial and not testing
any ostree functionality whatsoever. Presumably this was
a remnant from a time when the test case attempts to fetch
the payload over a local http connection.







local source tests: Removed test case for get_unique_key()
2017-09-02T00:21:48+00:00

Tristan Van Berkom
tristan.vanberkom@codethink.co.uk

2017-09-01T23:41:45+00:00

e54ab368e241c518015431251759013448196348

This somewhat arbitrarily tests what the local source generates
as a unique key but is not really the requirements of a unique
key. This is also subject to change and is a pain to update.

Instead this is pretty much handled by the cache key test anyway.





This somewhat arbitrarily tests what the local source generates
as a unique key but is not really the requirements of a unique
key. This is also subject to change and is a pain to update.

Instead this is pretty much handled by the cache key test anyway.