Loading
Commits on Source 54
-
Tristan Van Berkom authored
This is causing pytest to try to import the recently added app1.py from the pip related tests. This fails because it's not meant to be imported outside of the sandbox environment.
-
Tristan Van Berkom authored
setup.cfg: Add tests/integration/project to norecursedirs See merge request !682
-
Jonathan Maw authored
It would have been more convenient to store the quota size in the ArtifactCache, except that the scheduler needs the quota size and doesn't have access to the ArtifactCache.
-
Jonathan Maw authored
-
Jonathan Maw authored
-
Jonathan Maw authored
-
Jonathan Maw authored
Jonathan/cache cache size See merge request !679
-
Jonathan Maw authored
-
Jonathan Maw authored
Jonathan/cascache cell var from loop See merge request !686
-
-
Jonathan Maw authored
-
Jonathan Maw authored
Pipeline: Skip except_elements logic if no elements to except See merge request !688
-
These new images come with pinned versions of `pytest` and `pylint`: - `pylint`: `== 2.1.1` - `pytest`: `>= 3.7`
-
These packages should only be updated as a deliberate change and the code should be tested with the new versions to ensure that the test still pass. Any future updates should also happen in sync with the buildstream-docker-images repository so that the testsuite base images also enforce the same restrictions for the development requirements. Replaces !684.
-
Tristan Van Berkom authored
Restrict pylint/pytest versions and bump CI tags See merge request !689
-
Chandan Singh authored
Fill out those fields in `setup.py` that are required for publishing a package on PyPi. Part of #587.
-
Tristan Van Berkom authored
setup.py: Add fields required for publishing on PyPi See merge request !695
-
Tristan Van Berkom authored
Now we allow the notification to happen on any TERM which starts with 'xterm' or 'vte', and we only do it if the VTE_VERSION is >= 4600, where we know for sure that VTE will not print garbage on the terminal. Fixes #385
-
Tristan Van Berkom authored
_frontend/linuxapp.py: Fix special casing around desktop notification escape sequence Closes #385 See merge request !692
-
William Salmon authored
This patch just displays a better message than the default stack trace but dose not try to fix the problem. A further patch will be created but it effects versioneer so may take longer to land as it may need to go via versioneer mainline.
-
William Salmon authored
This has been done in a way that I hope might be able to be upstreamed in to versioneer. This is not garanteed but it would be good if it could be. Please see https://github.com/warner/python-versioneer/pull/186 and https://github.com/wsalmonct/python-versioneer/tree/feature/regexTags for further details.
-
William Salmon authored
Search for tags with the *.*.* patten for version See merge request !601
-
Sam Thursfield authored
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.
-
Tristan Van Berkom authored
Don't strip pathname from debug symbol files See merge request !697
-
Chandan Singh authored
Currently, running any setuptools commands using `setup.py` generates a warning like so: warning: manifest_maker: MANIFEST.in, line 21: unknown action 'dev-requirements.txt' The syntax is invalid and got accidentally introduced in !637 but it's a shame that this is not a warning and no obvious way to make it an error if there are invalid things in MANIFEST.in file. -
Chandan Singh authored
MANIFEST.in: Fix include for dev-requirements.txt See merge request !704
-
Tristan Van Berkom authored
When fixing terminal notifications, I had introduced a bug with accesses to `os.environ` which triggered KeyError, this patch fixes it.
-
Fixes #576.
-
Tristan Van Berkom authored
Improve error message for deleted open workspaces Closes #576 See merge request !703
-
Fixes #561
-
Tristan Van Berkom authored
Remove artifact extracts when artifact expires in cache Closes #561 See merge request !685
-
Mathieu Bridon authored
Buildstream uses the Terminal.does_styling attribute, which was only added in blessings 1.6. Blessings helpfully returns an empty string when calling an nonexistent attribute on the Terminal object, instead of failing. Because Fedora has blessings 1.5, Buildstream thought that my terminal couldn't handle styling, and just didn't print the status bar, silently. Specifying the minimum version avoids this silent failure.
-
Tristan Van Berkom authored
-
Tristan Van Berkom authored
Now that we only run pre-merge CI, it makes no sense to show a badge for the coverage and pipeline status of the last run of master. It would make sense to show a badge for the last pipeline which was run for the last merge request that was merged to master, but I don't see any feature to get that information.
-
Tristan Van Berkom authored
.gitlab-ci.yml: Avoid running tests in post-merge See merge request !709
-
Chandan Singh authored
Add a check to verify that the source distribution tarball that we generate installs corrctly. It is useful to do this check as this is the same tarball will be used when installing BuildStream via PyPI. This check also happens indirectly in the coverage job where we install BuildStream but this check makes it more explicit and will also cause the CI to fail early if the tarball is not correct.
-
Tristan Van Berkom authored
.gitlab-ci.yml: Verify that source tarball installs correctly See merge request !720
-
-
Tristan Van Berkom authored
tests/integration/source-determinism.py: Use cli_integration. See merge request !715
-
Tristan Van Berkom authored
This makes the integration tests use the same 'alpine' alias for the tests as we use in the examples, this avoids a redundant download of an extra alpine tarball in integration tests. This is a part of #603
-
Tristan Van Berkom authored
tests/integration/project: Use the same alias for the alpine tarball See merge request !722
-
Jim MacArthur authored
Staging may produce directories with less than 'rwx' permissions which will cause tempfile to throw an exception on deleting the temporary directory if not changed.
-
James Ennis authored
-
James Ennis authored
-
James Ennis authored
Correct crash after staging tars with read-only directories See merge request !713
-
James Ennis authored
-
James Ennis authored
'-k' flag not needed to run individual tests See merge request !714
-
Add instructions to install and update BuildStream python package via PyPI, and also make it the recommended method. Part of BuildStream/buildstream#587.
-
Chandan Singh authored
doc: Add instructions to install BuildStream via PyPI See merge request !717
-
Tom Pollard authored
Explicitly check that project.conf contains a name. This resolves the issue of the provenance check from _yaml.py incorrectly reporting the offending file as the default_config_node projectconfig.yaml when no name key exists in the pre_config_node dict.