[all-commits] [llvm/llvm-project] 458fa1: [Github] Allow CI to run different Python version ...

[Jannick Kremer via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 458fa12202868281f11680a18878d57defcccc9f
      https://github.com/llvm/llvm-project/commit/458fa12202868281f11680a18878d57defcccc9f
  Author: Jannick Kremer <jannick.kremer at mailbox.org>
  Date:   2024-08-08 (Thu, 08 Aug 2024)

  Changed paths:
    M .github/workflows/libclang-python-tests.yml
    M .github/workflows/llvm-project-tests.yml

  Log Message:
  -----------
  [Github] Allow CI to run different Python version tests at once (#102455)

Previously, #77219 added a `python_version` parameter for the Github
Actions CI Ninja-based build tests. This is necessary to run component
tests on different Python versions, as is currently done by the only
user of this parameter, the [Libclang Python bindings
test](https://github.com/llvm/llvm-project/blob/main/.github/workflows/libclang-python-tests.yml).
The parameter is missing from the concurrency group of the
workflow, meaning that starting the workflow with two different Python
versions immediately cancels one of them, as pointed out by
https://github.com/llvm/llvm-project/pull/77219#issuecomment-1937105822.
This change fixes that problem by making the Python version part of the
concurrency group key, and removes the superfluous concurrency group
from the calling workflow.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications