useless messages "run failed: sync issue" from espressif / github jira (BSP-761)

[dannybackx]

Board

N/A

Hardware Description

N/A

IDE Name

N/A

Operating System

N/A

Description

Such mails appear often and they're basically useless.

GitHub
[espressif/esp-bsp] Sync issue comments to JIRA workflow run
 
 
Sync issue comments to JIRA: All jobs have failed
 
 
	Sync Issue Comments to Jira 	

Sync issue comments to JIRA / Sync Issue Comments to Jira
Failed in 4 minutes and 17 seconds
	annotations for Sync issue comments to JIRA / Sync Issue Comments to Jira 1

Sketch

N/A

Other Steps to Reproduce

No response

I have checked existing issues, README.md and ESP32 Forum

• I confirm I have checked existing issues, online documentation and Troubleshooting guide.

[github-actions]

Hi @dannybackx! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.

---

I'm sorry, but the provided knowledge sources do not contain information regarding internal GitHub-to-JIRA workflow failures, such as the "Sync issue comments to JIRA" error mentioned in your query.

The documentation provided focuses on:

• Hardware and software troubleshooting for ESP-IDF, such as resolving gibberish output in the monitor by adjusting the Main XTAL Frequency [Getting Started With ESP-IDF].
• Debugging issues, including OpenOCD "Out of Sync" errors caused by external board resets [Blink Example With Coverage Info (Gcov)] or flasher stub execution failures [Flasher Stub Execution Problem].
• Tool-specific troubleshooting, such as network timeouts or missing dependencies when building esptool [Copilot Instructions for esptool].

Because this issue appears to be related to the internal automation of the espressif/esp-bsp repository rather than a technical issue with a chip or the SDK, I cannot provide a specific resolution based on the available documents. I recommend that the maintainers of that specific repository be notified directly through the GitHub issue so they can inspect their CI/CD workflow configurations.

[PetrESP]

Hello @dannybackx,

I am sorry that you're received this notification which was not directed for you.
You were notified about it since you were the one creating the issue.
I've fixed the cause of failure but sadly there currently doesn't seem to be a way to not send notifications to authors on certain job failures.