summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Be more explicit on where the gcc dirs are in the bootstrapjonathan/source-bundle-workaroundJonathan Maw2017-09-141-0/+4
| | | | | | It's possible for the gcc binary to be in /tools, but the libs we want to be in /usr/lib. gcc will by default look in a dir related to where it found the gcc binary.
* .coveragerc: Indicate that we use multiprocessingTristan Van Berkom2017-09-061-2/+10
| | | | | | | The coverage reports do not include codepaths reached by forked processes with multiprocessing unless we configure this, now we have a more accurate report (and up from 69% to 73% !)
* doc/source/install.rst: Fixing docs for required OSTree versionTristan Van Berkom2017-09-051-6/+1
| | | | | | | We require a newer version of OSTree now so the old note in the install.rst doesnt make sense anymore. This fixes issue #88
* tests/frontend/buildcheckout.py: Run tests in strict/non-strict modeTristan Van Berkom2017-09-051-9/+21
|
* source-bundle: don't use a subdirectory of {build_root}Charles Bailey2017-09-051-3/+3
| | | | | | | | | | Use {build_root} itself and not a subdirectory of {build_root} for the build area used in the source-bundle generated build scripts. This is consistent with what %{build-root} is expanded to when generating the build scripts. Fixes issue #67
* tests/completions/completions.py: Testing more completion casesTristan Van Berkom2017-09-0510-17/+114
|
* _frontend/complete.py: Fixing completions of subdirectory trees in element ↵Tristan Van Berkom2017-09-051-4/+17
| | | | | | | | | | | subdirs When completing .bst files in subdirectories of an 'element-path', we need to take the element path into consideration when testing the results of os.listdir() for os.path.isdir(). This makes directories behave like directories when completing subdirs of project element paths.
* tests/completions/completions.py: Adding new test for bash completionsTristan Van Berkom2017-09-0510-0/+272
|
* tests/frontend/pull.py: Added test case for testing `bst pull`Tristan Van Berkom2017-09-051-0/+145
|
* tests/frontend/push.py: Adding test for `bst push`Tristan Van Berkom2017-09-051-0/+98
|
* _pipeline.py: Raise pipeline error in pull/pushTristan Van Berkom2017-09-051-2/+2
| | | | | Instead of trying to fire a MessageType.FAIL without an elapsed parameter, and then not returning from the push()/pull() methods.
* frontend test project.conf: Use a more neutral and sensible project nameTristan Van Berkom2017-09-051-1/+1
|
* tests/testutils/runcli.py: Now the cli can set the environment and cwd for a runTristan Van Berkom2017-09-051-7/+40
|
* tests/testutils/runcli.py: Print CLI commands unconditionallyTristan Van Berkom2017-09-051-5/+5
| | | | We want to see them in failed test logs even if they succeeded.
* tests/testutils/runcli.py: Added get_element_key() method to fetch cache keyTristan Van Berkom2017-09-051-0/+13
|
* artifactcache.py: Special casing local pull & pushTristan Van Berkom2017-09-051-4/+18
| | | | | | | | | | It's interesting to keep the local directory push & pull codepaths alive for the sake of testing everything that calls into the artifact cache. For this reason, even when the artifact cache is "offline", it should be possible to pull and push to it if it is a local artifact share.
* tests/testutils/artifactshare.py: Added scaffolding for artifact sharesTristan Van Berkom2017-09-052-0/+107
| | | | | So we can create artifact shares and use them easily in test cases for pushing and pulling artifacts from a share.
* _frontend/main.py: special case test suite for completionsTristan Van Berkom2017-09-051-3/+16
| | | | | | | If we are executing completions in the context of running tests, dont use the fast exit path. Also some docstring fixups for push/pull commands
* _frontend/complete.py: Return whether completions were handled instead of ↵Tristan Van Berkom2017-09-051-34/+6
| | | | | | | | | | exiting Leave that choice to the calling code. Also some additional cleanup. Removed some bits of code borrowed from click but unused in this context, just because it's futzing up the coverage reports.
* setup.{cfg,py}: Bring back BST_TEST_SUITE env variableTristan Van Berkom2017-09-052-0/+3
| | | | Turns out we do need this in some corner cases
* Restructuring tests using the Repo and CliTristan Van Berkom2017-09-046-22/+18
| | | | | | Make all the test batteries which run on all the source backends we have repo scaffoldings for discover the list of Repo implementations automatically.
* tests/frontend/workspace.py: Adding test for `bst workspace` familyTristan Van Berkom2017-09-041-0/+192
|
* _frontend/widget.py: Removed pretty printing of workspace listTristan Van Berkom2017-09-041-17/+0
|
* _frontend/main.py: `bst workspace list` in machine readable format.Tristan Van Berkom2017-09-041-9/+14
| | | | | | | | | | It's important to be able to programatically interact with buildstream for things, that includes managing workspaces. This commit just dumps some serialized yaml instead of doing the pretty printing. This closes issue #55
* _frontend/main.py: Only prompt user when interactiveTristan Van Berkom2017-09-041-4/+7
| | | | | In both workspace_close() and workspace_reset() we do prompts, but these need to also be usable without human interaction.
* source.py: Consider workspaced sources with missing content inconsistentTristan Van Berkom2017-09-041-2/+13
| | | | | | | Avoid trying to calculate cache keys and then running into an error by just considering workspaces with missing content to be inconsistent. This fixes issue #80
* _yaml.py: Added load_data()Tristan Van Berkom2017-09-041-5/+12
| | | | Shared with _yaml.load(), but does not require a file on disk.
* _yaml.py: Make _yaml.dump() optionally dump to stdoutTristan Van Berkom2017-09-041-4/+8
|
* element.py: Use the BST_ARTIFACT_VERSION declared in the project.py moduleTristan Van Berkom2017-09-041-7/+2
|
* project.py: Declare main BST_ARTIFACT_VERSION hereTristan Van Berkom2017-09-041-8/+17
| | | | | Instead of hiding it away in the Element constructor, I want this to be easy to find.
* tests/sources/ostree.py: Removed test and data.Tristan Van Berkom2017-09-046-193/+0
| | | | | | | | 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/testutils/repo/ostree.py: Skip tests if the ostree cli is not installedTristan Van Berkom2017-09-041-0/+7
|
* cachekey.py: Fix broken logic of excluding testsTristan Van Berkom2017-09-041-2/+2
| | | | Skip the tests if we DONT have bzr or git, not if we DO.
* tests/cachekey/cachekey.py: Skip if not all plugins are availableTristan Van Berkom2017-09-041-0/+6
|
* tests/testutils/repo/git.py: Skip tests if git is not installedTristan Van Berkom2017-09-041-0/+8
|
* tests/testutils/repo/bzr.py: Skip tests if bzr is not installedTristan Van Berkom2017-09-041-0/+8
|
* tests/source/git.py: Skip if git is not availableTristan Van Berkom2017-09-041-0/+12
|
* tests/sources/bzr.py: Use site.py to determine presence of bzrTristan Van Berkom2017-09-041-8/+1
|
* testutis/site.py: A location for checking the presense of host featuresTristan Van Berkom2017-09-041-0/+22
|
* HACKING.rst: Adding a little reminder of how to invoke specific testsTristan Van Berkom2017-09-041-0/+6
|
* tests/frontend/track.py: Added test case for `bst track`Tristan Van Berkom2017-09-041-0/+57
|
* tests/frontend/fetch.py: Added tests for `bst fetch`Tristan Van Berkom2017-09-041-0/+50
|
* tests/frontend/compose_splits.py: Adding some simple artifact splitting test.Tristan Van Berkom2017-09-043-0/+69
| | | | This adds a couple of extra elements to the test data project.
* tests/frontend/show.py: Added test for `bst show`Tristan Van Berkom2017-09-041-0/+55
|
* tests/frontend/buildcheckout.py: Added tests for `bst build` and `bst checkout`Tristan Van Berkom2017-09-041-0/+78
|
* tests/frontend/project: Adding project data for frontend testsTristan Van Berkom2017-09-047-0/+47
| | | | This adds a test project for the frontend tests to share
* tests/frontend/version.py: Use the fixture to run buildstreamTristan Van Berkom2017-09-041-11/+3
|
* tests/frontend/help.py: Use the fixture to run buildstreamTristan Van Berkom2017-09-041-13/+5
|
* tests/cachekey/cachekey.py: Use the cli runner fixture here.Tristan Van Berkom2017-09-041-15/+5
|
* tests/testutils/repo module: New module for Source support scaffoldingTristan Van Berkom2017-09-046-0/+258
| | | | Currently comes with a Repo() abstract class and a git implementation
View Lorry Controller Status