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

Running repro in parallel #68

Closed
kpcyrd opened this issue Apr 21, 2020 · 6 comments
Closed

Running repro in parallel #68

kpcyrd opened this issue Apr 21, 2020 · 6 comments

Comments

@kpcyrd
Copy link
Member

kpcyrd commented Apr 21, 2020

I'm trying to run repro multiple times (giving each their own $BUILDDIRECTORY) for mass rebuilds but I ran into issues with:

Failed to allocate scope: Unit root.scope already exists

It seems this is because repro builds in /var/lib/repro/root, with root then becoming the machine name in nspawn, which has to be unique.

@Foxboron
Copy link
Member

Foxboron commented Apr 21, 2020

Two problems here

  • root scope is because we havent added the --empheral option
  • How do we set a unique build directory? Both devtools and repro currently use the username for the overlays.

@FFY00
Copy link
Member

FFY00 commented Apr 21, 2020

This would also be a good improvement to devtools, repro should follow devtools.

The solution here would be to generate an unique directory, eg. user-sdf78fse. This directory would be removed after the build, we could also ship a timer to cleanup unlocked directories in case the process exited before the directory was removed.

@Foxboron
Copy link
Member

I have also been contemplating just using $$ and use the PID of the process.

@Foxboron
Copy link
Member

Frankly, wouldn't $USER-$$ solve this? Is there any need for a more unique name for these directories?

@FFY00
Copy link
Member

FFY00 commented Apr 22, 2020

Just $$ works but I prefer $USER-$$. I don't see any drawbacks from this approach.

@Foxboron
Copy link
Member

Implemented with 6299e1e

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

3 participants