Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't seem to work anymore since github is not showling live logs #174

Open
CloseChoice opened this issue Sep 10, 2023 · 7 comments
Open

Comments

@CloseChoice
Copy link

This was a fantastic resource, but github somehow changed the way they log stuff and since I cannot see any logs of the currently running step I cannot access the server.

Is there a workaround for this?

@CloseChoice
Copy link
Author

CloseChoice commented Sep 10, 2023

Okay, one can use the detached mode in combination with a long sleep command as a kind of a replacement for the previous behaviour.
This is how I use it currently:

jobs:
  run-e2e-tests-prod:
    timeout-minutes: 60
    runs-on: ubuntu-latest
    steps:
      - <some_steps>
      - name: Setup tmate session
        uses: mxschmitt/action-tmate@v3
        with:
          detached: true
      - name: sleep forever
        run: |
          sleep 3600

Of course this is a poor replacement, since previously I could exit the session and immediatly check if my changes achieved the desired result, here I have to wait for the sleep command to finish (but one could probably build a loop where an environment variable is checked that we could set in the tmate session, but I leave this to somebody else)

@sebffischer
Copy link

For me it does not work with firefox but when I open the github logs with my iphone on safari they are shown.

@bramtayl
Copy link

Works in chrome but not firefox for me

@GilbertoAristizabalEmpire

Works in chrome but not firefox for me

Same here, works on chrome but not Firefox

@benbrackenc74
Copy link

@SanderVocke
Copy link

For me it seems to work fine with Firefox on any kind of runner.

@benbrackenc74
Copy link

This was fixed for me with an update to Firefox.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants