Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

2.168.0 does not work, permission issue, 2.165.2 worked fine

See original GitHub issue

Describe the bug Our CI testing started failing today without any change to our .yml or other setup; the only difference is that the GitHub runner was apparently updated from 2.165.2 (which worked fine) to 2.168.0 (which does not work).

We use the “checkout” v2 action, and this seems to fail. Inspecting the raw logs, we see:

2020-04-07T17:35:08.9585074Z [command]/usr/bin/git log -1
2020-04-07T17:35:08.9627094Z commit df7ef1ee005fead76cadffd594e05915452b3583
2020-04-07T17:35:08.9627421Z Author: XXXXXX YYYYYY <XXXXXXX@optimyze.cloud>
2020-04-07T17:35:08.9628050Z Date:   Tue Apr 7 10:11:38 2020 -0700
2020-04-07T17:35:08.9628138Z 
2020-04-07T17:35:08.9628245Z     Commit message
2020-04-07T17:35:08.9935859Z ##[error]Access to the path '/home/runner/runners/2.168.0/_diag/pages/2a8aec61-a697-428a-8919-a42ea1742359_02880bdf-4d66-515a-adeb-1569bc940d0f_1.log' is denied.

To Reproduce Steps to reproduce the behavior:

In our case, just creating a pull request that causes the action to run is enough.

Our .yml file looks like this:

(...)
jobs:
  run-unit-tests:
    runs-on: ubuntu-latest
    services:
      clickhouse:
        image: yandex/clickhouse-server
        ports:
          - 9000:9000
        volumes:
          - /:/var/lib/clickhouse
    container:
      image: [some-repository]/[some-image-name]:latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2
        with:
          path: github.com/optimyze/prodfiler

Expected behavior Existing .yml files that worked with version 2.165.2 should not break due to Github updating to 2.168.0.