search

agriyakhetarpal / issue-from-pytest-log

create issues from pytest-reportlog files
MIT License
0 stars 0 forks source link

Some debugging #1

Open agriyakhetarpal opened 5 months ago

agriyakhetarpal commented 5 months ago

Issues #3 and #4 have been opened. Now, I will update the input that I am passing to the action and change it from "${{ github.run_id }}-${{ matrix.os }} failed" to something else. If it will be different, we should see two new issues.

Edit: renamed it to "${{ github.run_id }}-${{ matrix.os }} did not pass"

Edit 2: there we go, we have two new issues. 🎉 #5 and #6.

agriyakhetarpal commented 5 months ago

Okay, we can't seek 500,000 issues, just the first 100 ones. The new issue input, i.e., "${{ github.run_id }}-${{ matrix.os }} did not pass" created two new issues, #6 and #7, as expected. Now, I will update the input to something generic again, say, "Nightly CI failure" so that it is not specific to the workflow, and then trigger CI on two further commits.

Then, we should see just one issue being opened on the first commit, and the second commit should update that issue. This is a test for the original functionality.

agriyakhetarpal commented 5 months ago

ea7908fd98aab5d3a84c764819973c834aea9271 just created issue #9 through https://github.com/agriyakhetarpal/issue-from-pytest-log/actions/runs/8753255136. Now, I'll push another random commit, and that will trigger CI again, and we should see the same issue being updated.

agriyakhetarpal commented 5 months ago

The commit c360928ba29023e59519099e95f80589978a5e5d above triggered a new workflow run: https://github.com/agriyakhetarpal/issue-from-pytest-log/actions/runs/8753293174/job/24022707944

and it can be seen on https://github.com/agriyakhetarpal/issue-from-pytest-log/issues/9 that the issue description was edited just now, through this new run, and no new issue was opened, just as we intended. 🥳