Action runs but does nothing

[actions]

Action runs but does nothing

[Aylr]

@MaicolBen Were you ever able to get this working?

[MaicolBen]

No, still not working, considering switching back to the bot one

[Aylr]

Thanks. I'm going to experiment with some of the forks. I'll let you know what I find.

[Aylr]

I got this to work! The key is that the javascript file path was missing on release 1.1.0. Add the main: 'lib/main.js' to the keys under the with section.

name: "Close stale issues"
on:
  issues:
    types: [opened, reopened]
  schedule:
  - cron: "*/15 * * * *"

jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/[email protected]
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        ...
        main: 'lib/main.js'

[MaicolBen]

still doesn't work, I believe I tried with the previous version of this action as well

[Aylr]

Unfortunately I only got it to run on some repos. This is very flaky and seems like it isn't maintained at the moment.

[MaicolBen]

No problem, thanks, feel free to close the issue, I switched back to the bot.

[Aylr]

Mind if I ask which bot?

[MaicolBen]

https://github.com/probot/stale

[hross]

If you set the secret ACTIONS_STEP_DEBUG to true in your repo, you should be able to see more output. The action will tell you what it is doing and why. You can also set the debug-only option to test it without it messing with your issues.

If you get good output please paste in here so we can help you troubleshoot.

[Aylr]

@hross Thanks for the pointer to debug flags. I've done that (I think correctly) and still see no helpful output:
https://github.com/great-expectations/great_expectations/runs/596802285?check_suite_focus=true

Raw log:

2020-04-17T22:28:34.6125584Z ##[section]Starting: Request a runner to run this job
2020-04-17T22:28:35.0441848Z Requesting a hosted runner in current repository's account/organization with labels: 'ubuntu-latest', require runner match: True
2020-04-17T22:28:35.1619552Z Labels matched hosted runners has been found, waiting for one of them get assigned for this job.
2020-04-17T22:28:35.1920002Z ##[section]Finishing: Request a runner to run this job
2020-04-17T22:28:40.0184566Z Current runner version: '2.169.0'
2020-04-17T22:28:40.0206034Z ##[group]Operating System
2020-04-17T22:28:40.0206597Z Ubuntu
2020-04-17T22:28:40.0206810Z 18.04.4
2020-04-17T22:28:40.0207150Z LTS
2020-04-17T22:28:40.0207434Z ##[endgroup]
2020-04-17T22:28:40.0207814Z ##[group]Virtual Environment
2020-04-17T22:28:40.0208012Z Environment: ubuntu-18.04
2020-04-17T22:28:40.0208354Z Version: 20200406.2
2020-04-17T22:28:40.0208593Z Included Software: https://github.com/actions/virtual-environments/blob/ubuntu18/20200406.2/images/linux/Ubuntu1804-README.md
2020-04-17T22:28:40.0208760Z ##[endgroup]
2020-04-17T22:28:40.0209938Z Prepare workflow directory
2020-04-17T22:28:40.0426130Z Prepare all required actions
2020-04-17T22:28:40.0437212Z Download action repository 'actions/[email protected]'
2020-04-17T22:28:41.3788565Z ##[group]Run actions/[email protected]
2020-04-17T22:28:41.3788994Z with:
2020-04-17T22:28:41.3789553Z   repo-token: ***
2020-04-17T22:28:41.3789847Z   stale-issue-message: Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?\n\nThis issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
2020-04-17T22:28:41.3790242Z   stale-pr-message: Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?\n\nThis issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
2020-04-17T22:28:41.3790504Z   days-before-stale: 120
2020-04-17T22:28:41.3790716Z   days-before-close: 7
2020-04-17T22:28:41.3790897Z   stale-issue-label: stale
2020-04-17T22:28:41.3791130Z   stale-pr-label: stale
2020-04-17T22:28:41.3791399Z   exempt-issue-label: stalebot-exempt
2020-04-17T22:28:41.3791585Z   operations-per-run: 30
2020-04-17T22:28:41.3791769Z   main: lib/main.js
2020-04-17T22:28:41.3791898Z   debug-only: true
2020-04-17T22:28:41.3792121Z env:
2020-04-17T22:28:41.3792316Z   ACTIONS_STEP_DEBUG: true
2020-04-17T22:28:41.3792499Z ##[endgroup]
2020-04-17T22:28:43.7077284Z Cleaning up orphan processes

[hross]

@Aylr from your log it looks like you are pinned to v1.1.0 which doesn't have debug output. You should pin to stale@v2. I submitted a PR to your repo.

[hross]

Also, v2 should resolve some of the above issues (javascript file path)

[MaicolBen]

Thank you to ACTIONS_STEP_DEBUG I discovered that was a missing stale-pr-message which I had the issue one, so it'd be great to be notified instead of using the debug flag

[Aylr]

@hross Thanks a ton for the PR that bumps the version. I have enabled the debug output, and I'm still at a loss as to why no labels are being applied. Here's a link to the run: https://github.com/great-expectations/great_expectations/actions/runs/95701394 and the raw debug log output: https://pipelines.actions.githubusercontent.com/hkXi2FzNCSfhQv7obSWa9OUyRF4zRLVKhgykrJMpS9j3VKaVaD/_apis/pipelines/1/runs/868/signedlogcontent/3?urlExpires=2020-05-04T22%3A59%3A11.8934671Z&urlSigningMethod=HMACV1&urlSignature=TCE2wNbVxggmeZrtH6KkhQeY0Kjom8zmJZObbcYzKXc%3D

[hross]

@Aylr from looking at your workflow file here:

https://github.com/great-expectations/great_expectations/actions/runs/95701394/workflow

It looks like you have 120 days until stale and then 7 days until close. The bot won't close anything that isn't already marked stale so you are basically telling it to wait 120 days to stale something and then close it. That is kind of confusing but it's to prevent accidentally closing issue that aren't stale. I wonder if we can make the docs more clear or change the close parameter name to make it more obvious.

[Aylr]

Thanks for your excellent help on this @hross!