1. 03 Jan, 2019 1 commit
  2. 02 Jan, 2019 7 commits
  3. 31 Dec, 2018 8 commits
  4. 26 Dec, 2018 17 commits
  5. 21 Dec, 2018 1 commit
  6. 20 Dec, 2018 6 commits
    • Tom Pollard's avatar
      ac995236
    • Chandan Singh's avatar
      Merge branch 'chandan/fix-warning' into 'master' · cd4889af
      Chandan Singh authored
      Fix Deprecation warnings from regex module
      
      See merge request !1010
      cd4889af
    • Chandan Singh's avatar
      buildstream/utils.py: Fix regex Deprecation Warning · e8055a56
      Chandan Singh authored
      Specify flags at the start of the expression as per the recommendation
      of the standard library.
      
      Without this patch, we currently get the following warning:
      
      ```
      tests/examples/junctions.py::test_open_cross_junction_workspace
        /builds/BuildStream/buildstream/dist/buildstream/buildstream/utils.py:213: DeprecationWarning: Flags not at the start of the expression '\\/[^/]*\\Z(?ms)'
          regexer = re.compile(expression)
      ```
      e8055a56
    • Chandan Singh's avatar
      tests/frontend/logging.py: Fix regex Deprecation Warning · c05d8b4f
      Chandan Singh authored
      Use raw strings for regex searches, which is the preferred way to do
      regular expressions in Python.
      
      Without this patch, currently we get the following warnings:
      
      ```
      tests/frontend/logging.py:44
        /builds/BuildStream/buildstream/dist/buildstream/tests/frontend/logging.py:44: DeprecationWarning: invalid escape sequence \[
          m = re.search("\[\d\d:\d\d:\d\d\]\[\]\[\] SUCCESS Checking sources", result.stderr)
      
      tests/frontend/logging.py:80
        /builds/BuildStream/buildstream/dist/buildstream/tests/frontend/logging.py:80: DeprecationWarning: invalid escape sequence \d
          m = re.search("\d\d:\d\d:\d\d,\d\d:\d\d:\d\d.\d{6},\d\d:\d\d:\d\d,,,SUCCESS,Checking sources", result.stderr)
      ```
      c05d8b4f
    • Angelos Evripiotis's avatar
      Merge branch 'aevri/rm-autoinit' into 'master' · e0c575c4
      Angelos Evripiotis authored
      BREAK: remove auto-init behaviour
      
      Closes #826
      
      See merge request !1015
      e0c575c4
    • Angelos Evripiotis's avatar
      BREAK: remove auto-init behaviour · 46efc91d
      Angelos Evripiotis authored
      In the event that the project could not be found, stop BuildStream from
      asking if the user would like to create a new project. Exit with error
      instead, and give a hint to the user in case they're new.
      
      As proposed on the mailing list here:
      https://mail.gnome.org/archives/buildstream-list/2018-December/msg00082.html
      
      The new interaction looks like this:
      
          $ bst show nonsuch.bst
          No project found. You can create a new project like so:
      
              bst init
      
          Error loading project: None of ['project.conf', '.bstproject.yaml']
          found in '/src/temp/blah' or any of its parent directories
      
      Fixes #826
      46efc91d