[Bug]: Missing PR comments
@cicdguy ci sta già lavorando.
Dal 9/2/2024.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
What happened?
After some time of using the action with great success, the PR comments suddenly disappeared. The logs from the action run don't contain any explicit errors, and all steps seem to work as expected. We tried deleting the coverage branch and updating to the latest version of the action but the behavior persists.
The only potentially-related messages I was able to find in the logs (even with Debug mode enabled) are the following:
fatal: a branch named '_xml_coverage' already exists:
▼ Run git config --global user.email "41898282+github-actions[bot]@users.noreply.github.com"
git config --global user.email "41898282+github-actions[bot]@users.noreply.github.com"
git config --global user.name "github-actions[bot]"
# Switch to the branch if it already exists
git switch _xml_coverage || true
git pull origin _xml_coverage || true
# Create the branch if it doesn't exist yet
git checkout --orphan _xml_coverage || true
# Ensure that the bare minimum components exist in the branch
mkdir -p data
touch README.md data/.gitkeep
# Copy necessary files and folders to a temporary location
mkdir -p /tmp/cfd24555d4f2483afc5f83f742e1eb02bfe120a8
echo "Copying data to /tmp/cfd24555d4f2483afc5f83f742e1eb02bfe120a8"
cp -r .git README.md data /tmp/cfd24555d4f2483afc5f83f742e1eb02bfe120a8
# Remove everything else
# Attribution: https://unix.stackexchange.com/a/77313
rm -rf ..?* .[!.]* *
# Restore files from the temporary location
echo "Copying data from /tmp/cfd24555d4f2483afc5f83f742e1eb02bfe120a8"
cp -r /tmp/cfd24555d4f2483afc5f83f742e1eb02bfe120a8/.git /tmp/cfd24555d4f2483afc5f83f742e1eb02bfe120a8/README.md /tmp/cfd24555d4f2483afc5f83f742e1eb02bfe120a8/data .
rm -rf /tmp/cfd24555d4f2483afc5f83f742e1eb02bfe120a8
git add --all -f
git commit -m "Update storage branch: $(date)" || true
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
env:
pythonLocation: /opt/hostedtoolcache/Python/3.11.7/x64
PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.11.7/x64/lib/pkgconfig
Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.7/x64
Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.7/x64
Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.7/x64
LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.11.7/x64/lib
##[debug]/usr/bin/bash --noprofile --norc -e -o pipefail /home/runner/work/_temp/d06e431e-a16d-4966-9068-38b881147dd1.sh
Switched to a new branch '_xml_coverage'
branch '_xml_coverage' set up to track 'origin/_xml_coverage'.
From https://github.com/exampleorg/repo
* branch _xml_coverage -> FETCH_HEAD
Already up to date.
fatal: a branch named '_xml_coverage' already exists
Copying data to /tmp/cfd24555d4f2483afc5f83f742e1eb02bfe120a8
Copying data from /tmp/cfd24555d4f2483afc5f83f742e1eb02bfe120a8
On branch _xml_coverage
Your branch is up to date with 'origin/_xml_coverage'.
nothing to commit, working tree clean
no pull request numbers given: skip step:
▼ Run marocchino/sticky-pull-request-comment@v2
with:
header: coverage/e2e/merged/coverage-e2e.xml
path: .coverage-output.final
append: false
recreate: false
delete: false
only_create: false
only_update: false
hide_details: false
hide: false
hide_and_recreate: false
hide_classify: OUTDATED
ignore_empty: false
skip_unchanged: false
follow_symbolic_links: false
GITHUB_TOKEN: ***
env:
pythonLocation: /opt/hostedtoolcache/Python/3.11.7/x64
PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.11.7/x64/lib/pkgconfig
Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.7/x64
Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.7/x64
Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.11.7/x64
LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.11.7/x64/lib
diff_storage_branch: 387-missing-coverage-comments-in-pull-requests
no pull request numbers given: skip step
Relevant log output
No response
Code of Conduct
- I agree to follow this project's Code of Conduct.
Contribution Guidelines
- I agree to follow this project's Contribution Guidelines.
Security Policy
- I agree to follow this project's Security Policy.
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 28
- Fork
- 14
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di insightsengineering/coverage-action
-
[Bug]: fetch-depth: 0 fetches unnecessarily deep and wide causes slowdown in "Fetch report" stepForse di nuovo libera @pawelru l’ha presa 363 giorni fa e non c’è nessuna pull request aperta. Apertabug
insightsengineering/coverage-action#55 · 2 assegnatari ·
-
[Feature Request]: Automatically clean up per-branch directories on the storage branch for deleted branchesForse di nuovo libera @pawelru l’ha presa 364 giorni fa e non c’è nessuna pull request aperta. Apertaenhancement
insightsengineering/coverage-action#54 · 2 assegnatari ·
-
[Feature Request]: Upgrade to latest pycoberturaForse di nuovo libera @pawelru l’ha presa 374 giorni fa e non c’è nessuna pull request aperta. Apertaenhancement
insightsengineering/coverage-action#53 · 2 assegnatari ·
-
[Feature Request]: Pull diff coverage report from CI artifactForse di nuovo libera @pawelru l’ha presa 444 giorni fa e non c’è nessuna pull request aperta. Apertaenhancement
insightsengineering/coverage-action#51 · 2 commenti · 3 assegnatari ·
-
[Bug]: Multiple coverage reports overwriting commentsForse di nuovo libera @cicdguy l’ha presa 486 giorni fa e non c’è nessuna pull request aperta. Apertadocumentation enhancement
insightsengineering/coverage-action#50 · 1 commento · 1 assegnatario ·