[all-commits] [llvm/llvm-project] 78205f: [libc++][Docker] Don't actually start using a newe...

[Louis Dionne via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 78205faf54d336c1ca86ceb8bbcf86188feec2f6
      https://github.com/llvm/llvm-project/commit/78205faf54d336c1ca86ceb8bbcf86188feec2f6
  Author: Louis Dionne <ldionne.2 at gmail.com>
  Date:   2022-02-04 (Fri, 04 Feb 2022)

  Changed paths:
    M libcxx/utils/ci/Dockerfile

  Log Message:
  -----------
  [libc++][Docker] Don't actually start using a newer compiler in the CI

To ensure a smooth transition without breaking CI, we should use explicitly
versioned Clangs in the CI jobs definition instead, since that's a change
we can actually test in the CI.

So instead of bumping the compiler version from the Docker image, use
the same version as before by default, and we can bump it from the CI
job definition once all the nodes are running the new image.