================
@@ -0,0 +1,70 @@
+name: "LLDB Python Lint"
+
+permissions:
+ contents: read
+
+on:
+ pull_request:
+ branches:
+ - main
+ - 'users/**'
+ paths:
+ - 'lldb/test/API/**'
+
+jobs:
+ code_linter:
+ if: github.repository_owner == 'llvm'
+ runs-on: ubuntu-24.04
+ defaults:
+ run:
+ shell: bash
+ container:
+ image: 'ghcr.io/llvm/ci-ubuntu-24.04-lint'
+ timeout-minutes: 60
+ concurrency:
+ group: ${{ github.workflow }}-${{ github.ref }}
+ cancel-in-progress: true
+ steps:
+ - name: Fetch LLVM sources
+ uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 #
v6.0.1
+ with:
+ fetch-depth: 2
+
+ - name: Setup python
+ uses: actions/setup-python@83679a892e2d95755f2dac6acb0bfd1e9ac5d548 #
v6.1.0
+ with:
+ python-version: '3.14'
+
+ - name: Install dependencies
+ run: |
+ python3.14 -m pip install --break-system-packages --require-hashes
-r ./llvm/utils/git/requirements_pylint.txt
----------------
DavidSpickett wrote:
> I saw some other LLVM Dockerfiles do it, so thought it would be OK.
Probably is most of the time, in these throw away environments.
> But I'd certainly love to fix it. It's quite finicky to debug all this, so I
> moved on from it.
Certainly can sympathise with that. Pushing YAML to production is one of the
worst debugging experiences.
https://github.com/llvm/llvm-project/pull/182003
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
