On 2024-06-27 17:07, Jan Beulich wrote:
On 27.06.2024 15:46, GitLab wrote:
Pipeline #1350627221 has failed!
Project: xen ( https://gitlab.com/xen-project/xen )
Branch: staging ( https://gitlab.com/xen-project/xen/-/commits/staging
)
Commit: 402e4732 (
https://gitlab.com/xen-project/xen/-/commit/402e473249cf62dd4c6b3b137aa845db0fe1453a
)
Commit Message: x86/traps: address violations of MISRA C Rule 2...
Commit Author: Nicola Vetrini
Committed by: Jan Beulich ( https://gitlab.com/jbeulich )
Pipeline #1350627221 (
https://gitlab.com/xen-project/xen/-/pipelines/1350627221 ) triggered
by Ganis ( https://gitlab.com/ganis )
had 1 failed job.
Job #7202274595 (
https://gitlab.com/xen-project/xen/-/jobs/7202274595/raw )
Stage: analyze
Name: eclair-x86_64
Without any earlier errors that I could spot the build log ends in
section_end:1719492504:step_script
[0Ksection_start:1719492504:upload_artifacts_on_failure
[0K[0K[36;1mUploading artifacts for failed job[0;m[0;m
[32;1mUploading artifacts...[0;m
ECLAIR_out/*.log: found 2 matching artifact files and directories[0;m
[0;33mWARNING: ECLAIR_out/*.txt: no matching files. Ensure that the
artifact path is relative to the working directory
(/builds/xen-project/xen)[0;m
*.log: found 2 matching artifact files and directories[0;m
Uploading artifacts as "archive" to coordinator... 201 Created[0;m
id[0;m=7202274595 responseStatus[0;m=201 Created token[0;m=glcbt-66
[32;1mUploading artifacts...[0;m
[0;33mWARNING: gl-code-quality-report.json: no matching files. Ensure
that the artifact path is relative to the working directory
(/builds/xen-project/xen)[0;m
[31;1mERROR: No files to upload [0;m
section_end:1719492506:upload_artifacts_on_failure
[0Ksection_start:1719492506:cleanup_file_variables
[0K[0K[36;1mCleaning up project directory and file based
variables[0;m[0;m
section_end:1719492506:cleanup_file_variables
[0K[31;1mERROR: Job failed: exit code 137
[0;m
IOW - some failure somewhere, but nothing noticeable in the log file.
Is
this an expected thing for this specific job?
No, and and I noticed no failure on our end either.
I saved the logs, so I would try running it again to see if it
reproduces.
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
