test: bazel

[erikburt]

Requires

Resolves

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[github-actions]

AER Report: CI Core

aer_workflow , commit , Detect Changes , Clean Go Tidy & Generate , lint , Core Tests (ubuntu-latest) , SonarQube Scan

1. Bazel run command not in workspace:[lint]

Source of Error:

Run Bazel Buildifier (Lint)	2024-10-24T22:23:42.8479852Z ERROR: The 'run' command is only supported from within a workspace (below a directory having a WORKSPACE file).
Run Bazel Buildifier (Lint)	2024-10-24T22:23:42.8481380Z See documentation at https://bazel.build/concepts/build-ref#workspace
Run Bazel Buildifier (Lint)	2024-10-24T22:23:42.9063416Z ##[error]Process completed with exit code 2.

Why: The Bazel run command was executed outside of a Bazel workspace, which requires a WORKSPACE file in the directory or a parent directory.

Suggested fix: Ensure the Bazel command is executed within a directory containing a WORKSPACE file or adjust the script to navigate to the correct directory before running the command.

2. Unable to resolve action repository:[Clean Go Tidy & Generate]

Source of Error:

Set up job	2024-10-24T22:22:21.8908215Z ##[error]Unable to resolve action bazelbuild/setup-bazel, repository not found

Why: The GitHub Action bazelbuild/setup-bazel could not be found, possibly due to a typo in the action name or the repository being unavailable.

Suggested fix: Verify the action name and repository URL in the workflow configuration file. Ensure the action exists and is correctly referenced.

3. Syntax error in shell script:[Core Tests (ubuntu-latest)]

Source of Error:

Get list of changed files	2024-10-24T22:23:25.7692491Z /home/runner/work/_temp/42a21201-4697-44b1-826e-0151319b8360.sh: line 7: syntax error: unexpected end of file
Get list of changed files	2024-10-24T22:23:25.7705058Z ##[error]Process completed with exit code 2.

Why: There is a syntax error in the shell script, likely due to a missing or unmatched quotation mark, parenthesis, or bracket.

Suggested fix: Review the shell script for syntax errors, ensuring all quotations, parentheses, and brackets are properly closed and matched.