Re: xen | Failed pipeline for staging | 402e4732

[Nicola Vetrini <nicola.vetrini@xxxxxxxxxxx>]

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
> section_start:1719492504:upload_artifacts_on_failure
> Uploading artifacts for failed job
> Uploading artifacts...
> ECLAIR_out/*.log: found 2 matching artifact files and directories
> WARNING: ECLAIR_out/*.txt: no matching files. Ensure that the 
> artifact path is relative to the working directory 
> (/builds/xen-project/xen)
> *.log: found 2 matching artifact files and directories
> Uploading artifacts as "archive" to coordinator... 201 Created  
> id=7202274595 responseStatus=201 Created token=glcbt-66
> Uploading artifacts...
> WARNING: gl-code-quality-report.json: no matching files. Ensure 
> that the artifact path is relative to the working directory 
> (/builds/xen-project/xen)
> ERROR: No files to upload                         
> section_end:1719492506:upload_artifacts_on_failure
> section_start:1719492506:cleanup_file_variables
> Cleaning up project directory and file based 
> variables
> section_end:1719492506:cleanup_file_variables
> ERROR: Job failed: exit code 137
> 
>
> 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)