Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

semgrep CI failing, with no logs generated. #20788

Open
Praveen-Brcm opened this issue Nov 13, 2024 · 0 comments
Open

semgrep CI failing, with no logs generated. #20788

Praveen-Brcm opened this issue Nov 13, 2024 · 0 comments
Labels
ci MSFT Triaged this issue has been triaged

Comments

@Praveen-Brcm
Copy link
Contributor

Description

semgrep check is failing, which is blocking the code PR merge.
semgrep failure is not generating the log or showing the specific details about the failure.

Steps to reproduce the issue:

  1. Create a PR
  2. Submit the code to sonic-build image
  3. see that required check is failing

Describe the results you received:

For the PR's : belwo mentioned PR's CI merge is failing due to required check "semgrep" is failing.
#18627
#18628
#18633

Below is the log reporting that semgrep is failing.

Changes approved
1 approving review by reviewers with write access.
1 approval
1 pending reviewer
Some checks were not successful
1 failing, 19 successful, and 1 neutral checks
@github-actions
Semgrep / Semgrep (pull_request) Failing after 29s
Required

While trying to get more details about the failure, the corresponding log file is not present.

Details
The failure is not indicating specific details or logs, the log file is not found.
Semgrep
failed on May 14 in 29s
Search logs
1s
Error: The log was not found. It may have been deleted based on retention settings.
9s
Error: The log was not found. It may have been deleted based on retention settings.
7s
Error: The log was not found. It may have been deleted based on retention settings.
10s
Error: The log was not found. It may have been deleted based on retention settings.
0s
Error: The log was not found. It may have been deleted based on retention settings.
1s
Error: The log was not found. It may have been deleted based on retention settings.
0s
Error: The log was not found. It may have been deleted based on retention settings.

Describe the results you expected:

semgrep to scucced or provide the details for the failures to debug if there any issues.

@adyeung adyeung added ci Triaged this issue has been triaged MSFT labels Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci MSFT Triaged this issue has been triaged
Projects
None yet
Development

No branches or pull requests

2 participants