Updating workflow file on master and rerunning an action still shows old workflow file

Code to Cloud GitHub Actions
#1

The scenario is:

  1. GitHub action is triggered
  2. There’s a problem with the workflow file of said action and it fails
  3. Workflow file is updated on the master branch
  4. Rerun the action from step 2
  5. Clicking the “Workflow file tab” shows the workflow file before step 3 even though the rerun uses the workflow updated in step 3

The unexpected behavior for me here is showing the old workflow file instead of the one that’s currently running.

#2

Hi @davidtvs ,

Checked on my side, re-run failed workflow will still use the old workflow yaml. 

I used ‘actions/checkout@ v3’ to fail the workflow, and update with v2 which is the correct version. Re-run failed workflow still use old yaml, screenshot as below:

wrongyaml.png
wrongyaml.png987×314 19.8 KB

Could you please have a double check ? If the issue persists, please share your repo/workflow yaml for futher investigation.

Thanks.

#3

The action where I noticed the behavior is this one: https://github.com/davidtvs/pytorch-lr-finder/runs/694266910?check_suite_focus=true

It was failing on the step “Run actions/checkout@v2 - Fetching the repository”. The workflow file when it failed was this one. I actually re-ran multiple times before making changes to the workflow and the action always failed at that step. I then pushed a fix to master updating the workflow to this and re-ran the action which then ran correctly.

Is there a way I can access the logs of the previous re-runs?

I will also try to replicate the issue again.

#4

Hi @davidtvs ,

Thanks for your reply! The failed workflow yaml has same commit/tree ID with the fixed one, looks them are identical. Could you please let me know what did you fix?

And can you reproduce on your workflow now? the checkrun id is different between the failed workflow and re-run workflow, so you can record the id for comparison.

checkrunid.png

If it cannot be reproduced, i assume it could be a temporary problem.

Thanks

#5

Oops, I copy and pasted the same link twice:

The old workflow: https://github.com/davidtvs/pytorch-lr-finder/blob/22b5f609324cdb6c6587cf52a8b0a4ca0e9216c8/.github/workflows/flake8_lint.yml#L14

The new workflow: https://github.com/davidtvs/pytorch-lr-finder/blob/master/.github/workflows/flake8_lint.yml#L14

I updated the previous post with the correct links.

I’ll try to reproduce this issue later today.

#6

Seems like my post got deleted. Do you need me to post the steps to replicate again @weide-zhou?

#7

Hi @davidtvs,

No, i have your steps which deleted by the forum update.
I have raised an internal ticket to confirm the logic, will update once there’s a response.

Thanks for your patience!

#8

I have the same issue; changes to my workflow file are not honored at all.
Additionally, I cannot cancel the workflow! (See: Can't cancel github action workflow)

#9

I am having the same issue here… It would be nice if the re-run all jobs button would provide the option to re-run using the latest workflow.

1 Like
#10

If I recall correctly they run based on what was in the the branch you branch from at the time the branch was created. (So if you create a feature branch from master 3 days ago, it’ll run the workflows from 3 days ago when you PR.) So if you update master and want it in your PR then you need to rebase and force push.

#11

I have the same issue. Updated workflow is ignored (even on the branches that were created after the update)

#12

having the same issue that updated file on the same branch is ignored during re-runs. any updates on this issue?

#13

Same here. Would be nice to see some progress on this on this issue :upside_down_face:.

#14

Same issue. The updated workflow isn’t being used by Github Actions.

Action uses this file ArrangePy/publish-to-test-pypi.yml at ee5b7e6957dd12779cb44b91c7ff5e9dc55e7d85 · prashantsengar/ArrangePy (github.com)

While it should be using the newer version.

#15

Exactly. It’s very annoying that re-run does not use the updated workflow file. For example, if the workflow triggers on release, once has to create a new release just to debug the workflow. This is highly inconvenient.