summaryrefslogtreecommitdiff
path: root/tests/examples/autotools.py
Commit message (Collapse)AuthorAgeFilesLines
* tests: Drop chroot xfail/skipifJürg Billeter2019-12-311-2/+0
|
* tests: Drop buildbox xfailsJürg Billeter2019-12-101-1/+0
|
* Reformat code using BlackChandan Singh2019-11-141-23/+27
| | | | | | | 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 defaulttraveltissues/strictxfailDarius Makovsky2019-10-091-1/+1
| | | | tests: remove strict kwargs from xfail marks
* Revert "Mark xfail test that only fail in CI"Jürg Billeter2019-08-071-2/+0
| | | | This reverts commit b54c8cb07ca257be79940ffa70853bf75d2c287c.
* Mark xfail test that only fail in CIWilliam Salmon2019-07-251-0/+2
|
* Mark buildbox tests as xfail if they require non implemented featuresWilliam Salmon2019-07-251-3/+6
|
* test:utils/site: Consolidate IS_LINUX/WSL/Windows in a single siteBenjamin Schubert2019-06-061-2/+1
| | | | | | | | 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-061-2/+2
| | | | | | | 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-061-1/+2
| | | | | | | 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-161-2/+2
| | | | | | | | | - 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-301-2/+2
|
* tests: str(datafiles) instead of a longer thingAngelos Evripiotis2019-03-211-2/+2
| | | | | | | | | | | | | | | | | | | 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-201-1/+1
| | | | | 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-201-0/+3
| | | | | Pylint doesn't play well with pytest fixtures, we therefore need to silence this error.
* tests: Remove unused parameters in functionsBenjamin Schubert2019-03-011-2/+2
| | | | | For parameters that are required as part of an API, prefix them by "_" to make it clear they are unused
* Expose basic api for testing external plugins.phil/plugin-testing-apiPhil Dawson2019-02-081-2/+2
| | | | | | | | | | | | | | | | | | 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-221-1/+1
| | | | | | | | | | | 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-091-3/+1
| | | | | | | | | 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-051-4/+4
| | | | Also update tests to be consistent with this
* Ensure tests requiring bubblewrap are correctly markedBenjamin Schubert2018-11-201-3/+3
|
* Disable tests on example on other architectures than x86_64Valentin David2018-11-141-1/+5
|
* Don't strip pathname from debug symbol filesSam Thursfield2018-08-221-1/+3
| | | | | | | | | | | | | 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.
* doc: Adding part 3 of the getting started tutorial: autotools elementTristan Van Berkom2018-06-181-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
View Lorry Controller Status