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

Build step error in citgm-smoker configuration #4023

Open
lpinca opened this issue Feb 18, 2025 · 4 comments
Open

Build step error in citgm-smoker configuration #4023

lpinca opened this issue Feb 18, 2025 · 4 comments

Comments

@lpinca
Copy link
Member

lpinca commented Feb 18, 2025

The last build step in https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/configure generates the following error

+ find /home/iojs/tmp -mtime +3
+ xargs rm -rf
+ temp=/home/iojs/tmp/citgm_tmp
+ rm -rf '/home/iojs/tmp/citgm_tmp/*'
+ mkdir /home/iojs/tmp/citgm_tmp
mkdir: cannot create directory ‘/home/iojs/tmp/citgm_tmp’: No such file or directory
+ true

I think the issue is that the /home/iojs/tmp directory itself is deleted when the find /home/iojs/tmp -mtime +3 | xargs rm -rf command is executed. The problem then is that os.tmpdir() returns a directory that does not exists.

A quick fix might be to change find /home/iojs/tmp -mtime +3 | xargs rm -rf to find /home/iojs/tmp/* -mtime +3 | xargs rm -rf

Refs: nodejs/node#57005 (comment)
Refs: nodejs/node#57005 (comment)

@targos
Copy link
Member

targos commented Feb 18, 2025

I'm not sure that this is the source of the issue from nodejs/node#57005 (comment).

There are many places where the citgm process creates the directories it uses using mkdir(..., { recursive: true })

@lpinca
Copy link
Member Author

lpinca commented Feb 18, 2025

I honestly did not verify if the directory is recreated later.

@lpinca
Copy link
Member Author

lpinca commented Feb 18, 2025

@targos you are right. In this run https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3554/ the directory exists but it still fails so the issue behind nodejs/node#57005 (comment) must be another one.

@lpinca
Copy link
Member Author

lpinca commented Feb 18, 2025

I'm not sure if it makes sense to address this issue. Feel free to close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants