summaryrefslogtreecommitdiff
path: root/tests/examples
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Mark xfail test that only fail in CI"Jürg Billeter2019-08-075-18/+0
| | | | This reverts commit b54c8cb07ca257be79940ffa70853bf75d2c287c.
* Mark xfail test that only fail in CIWilliam Salmon2019-07-255-0/+18
|
* Mark buildbox tests as xfail if they require non implemented featuresWilliam Salmon2019-07-255-16/+29
|
* tests/examples/flatpak-autotools: rename HAVE_OSTREE to HAVE_OSTREE_PLUGINBenjamin Schubert2019-06-061-4/+6
| | | | | | What this checks does is check if the ostree plugin is installed and fully configured. Renaming to HAVE_OSTREE_PLUGIN makes it slightly more explicit
* tests/testutils/site: Remove completely and migrate HAVE_OSTREE to examplesBenjamin Schubert2019-06-061-1/+7
| | | | | | The only place needing to know about OSTREE is the flatpak-autotools for the documentation. We can therefore move the OSTREE business here and remove completely the site file, ending up with a single one left.
* test:utils/site: Consolidate IS_LINUX/WSL/Windows in a single siteBenjamin Schubert2019-06-067-13/+8
| | | | | | | | We currently have two sites file containing redundant information. - tests/testutils/site.py: Remove IS_{LINUX,WSL,WINDOWS} - rest: Change imports to import those from buildstream/tests/_utils/site.py
* test:utils/site: Consolidate MACHINE_ARCH variable in a single placeBenjamin Schubert2019-06-066-11/+12
| | | | | | | We have two different 'site' files that are redundant and both define some variables in BuildStream environment. Moving the MACHINE_ARCH to a single place.
* test:utils/site: Consolidate Bwrap environment variables in a single placeBenjamin Schubert2019-06-065-5/+10
| | | | | | | We have two different 'site' files that are redundant and both define some variables in BuildStream environment. Moving all the bubblewrap related ones in a single place.
* plugintestutils: Rename 'plugintestutils' package to 'testing'phil/rename-plugintestutilsPhil Dawson2019-04-167-11/+11
| | | | | | | | | - Rename plugintestutils to testing. - Don't run the tests from bst-plugins-template. This imports buildstream.plugintestutils so will have to be disabled to get through CI. This can be re nabled once bst-plugins-template has been patched.
* typo: writtent -> writtenBenjamin Schubert2019-03-306-13/+13
|
* tests: str(datafiles) instead of a longer thingAngelos Evripiotis2019-03-217-16/+16
| | | | | | | | | | | | | | | | | | | Replace some popular copypasta. This important-looking invocation: os.path.join(datafiles.dirname, datafiles.basename) is equivalent to this shorter invocation: project = str(datafiles) It seems like it's very popular copypasta, replace it with the shorter one thus: # Use 'gsed' or 'sed' etc. as appropriate for your system. git config --global alias.sub '!f() { git grep --name-only --null "$1" | gxargs --null gsed --in-place --expression "s/$1/$2/g" ; }; f' git sub 'os.path.join(datafiles.dirname, datafiles.basename)' 'str(datafiles)'
* tests:lint: disable 'unused-import' checks on pytest fixturesBenjamin Schubert2019-03-207-7/+7
| | | | | Pylint can't know that pytest's fixtures are used in a file and therefore reports false positives. Silencing all those errors
* tests:lint: silence redefined-outer-name in files using fixturesBenjamin Schubert2019-03-207-0/+21
| | | | | Pylint doesn't play well with pytest fixtures, we therefore need to silence this error.
* tests:lint: fix all ungrouped importsBenjamin Schubert2019-03-201-1/+1
|
* tests: Remove unused importsremove-dead-codeBenjamin Schubert2019-03-013-3/+0
|
* tests: Remove unused parameters in functionsBenjamin Schubert2019-03-017-13/+13
| | | | | For parameters that are required as part of an API, prefix them by "_" to make it clear they are unused
* tests: Remove unused variablesBenjamin Schubert2019-03-012-2/+0
|
* Expose basic api for testing external plugins.phil/plugin-testing-apiPhil Dawson2019-02-087-14/+14
| | | | | | | | | | | | | | | | | | We want external plugins to be able to make use of the core testing utils. This commit exposes the basic utilities which are currently in use in bst-external plugins. If necessary, more utilities could be exposed in the future. Moves the following files from tests/testutils/ to buildstream/plugintestingutils/: o runcli.py o integration.py As part of this, this commit makes the following changes to runcli.py and integration.py: o runcli.py: Fix linting errors o runcli.py: Add user facing documentation o Integration.py: Add user facing documentation
* Mark 'old' checkout command as obsoleteJames Ennis2019-01-224-4/+4
| | | | | | | | | | | This commit marks 'bst checkout' as a 'hidden' command. If used, the user will be prompted to use the new 'bst artifact checkout' command. All tests which used 'bst checkout' have been modified to use the new artifact sub-command. This partially solves #822.
* buildstream/data/projectconfig.yaml: Remove default strip-binariesJavier Jardón2018-12-093-9/+3
| | | | | | | | | They are too specific to be included by default Recommendation is if you are building in Linux is to use the ones begin used in the freedesktop-sdk project, for example See #645
* optionarch.py: update to use same arch names as SandboxConfigRaoul Hidalgo Charman2018-12-056-26/+26
| | | | Also update tests to be consistent with this
* Workspace CLI updateWilliam Salmon2018-11-212-3/+3
| | | | | | | This is to update the workspace CLI to as agreed on the mailing list https://mail.gnome.org/archives/buildstream-list/2018-September/msg00046.html This patch also introduces the default workspace directory.
* Ensure tests requiring bubblewrap are correctly markedBenjamin Schubert2018-11-206-19/+19
|
* Disable tests on example on other architectures than x86_64Valentin David2018-11-146-6/+32
|
* Don't strip pathname from debug symbol filesSam Thursfield2018-08-223-4/+10
| | | | | | | | | | | | | When GDB looks for debug symbols it looks for the full path of the file inside the configured debug-file-directory. For example, if the debug-file-directory is set to a default of /usr/lib/debug, and you are debugging /usr/bin/python3, GDB will look for its debug symbols at this location: /usr/lib/debug/usr/bin/python3. BuildStream has been putting all debug files inside /usr/lib/debug under their $(basename), so in the above example GDB would fail to find any debug symbols for /usr/bin/python3 because they would be in the incorrect locatoin of /usr/lib/debug/python3.
* local plugin: validate project pathsTiago Gomes2018-08-021-32/+0
| | | | | | The autotools example had to be copied over inside of the junction example, as referring to a path outside of the project directory is now disallowed.
* tests/examples/developing.py: Add tests for workspaces walkthroughphil/437-workspaces-tutorialPhil Dawson2018-08-011-0/+91
|
* tests/examples/junctions.py: Add tests for junctions walkthroughphil/437-junction-tutorialPhil Dawson2018-07-301-0/+84
| | | | This is part of the work towards issue #437.
* doc: Adding part 4 of the getting started tutorial: integration commandsTristan Van Berkom2018-06-251-0/+36
| | | | | This new section talks about how integration commands work and shows them at work.
* doc: Adding part 3 of the getting started tutorial: autotools elementTristan Van Berkom2018-06-182-0/+47
| | | | | | | | | This part of the tutorial uses a lot of the work from Phil Dawson and James Ennis, and uses their example submitted on merge request 499 as a basis to introduce the user to yaml composition and variable resolution. This is a part of issue #103
* doc: Adding part 2 of the getting started tutorialTristan Van Berkom2018-06-171-0/+36
| | | | | | | | | | | | | o doc/examples/running-commands: New example project of a `manual` build element o doc/sessions/running-commands.run: New session file to capture bst output o doc/source/sessions-stored: Added new generated sessions o doc/source/tutorial/running-commands.rst: New tutorial entry describing how commands are run in the sandbox o tests/examples/running-commands.py: Test case validating the tutorial's assertions
* doc: Adding part 1 of the getting started tutorialTristan Van Berkom2018-06-161-0/+29
| | | | | | | | | | | | | | | | | | | | | o doc/Makefile: Added new directory to collect rst files from o doc/examples/first-project: Added the "first-project" example project. o doc/source/sessions/first-project-*.html: Added the generated snippets o doc/source/using_tutorial.rst: Added the new main tutorial page o doc/source/tutorial/first-project.rst: Added part 1 of the tutorial here o tests/examples/first-project.py: Added test for the example project This is largely based on an example by Javier Jardón, which was submitted at https://gitlab.com/BuildStream/buildstream/merge_requests/323 Fixes #103
* tests/examples/flatpak-autotools.py: Workaround setuptools bugTristan Van Berkom2018-05-161-0/+18
| | | | | | Until the setuptools bug is fixed, symlinks are not included in source distributions - this works around the problem until which point we can use a setuptools version without the bug.
* doc: Add first example, building on a flatpak SDKalbfan2018-05-161-0/+49
This adds: o A ToC area for adding examples o The instructive example page for the first example o The example project under doc/examples o The corresponding integration test in tests/examples
View Lorry Controller Status