Skip to content

Conversation

stephenswat
Copy link
Member

In #4676, I implemented the possibility to use the code generation tooling for the ACTS code generation in an offline environment by creating a single virtual environment and reusing it across multiple custom targets. While this works naively, it introduces a race condition in which multiple threads modify the same virtual environment at the same time. In order to resolve this problem, I changed the build system to use a separate virtual environment for every code generation target.

In acts-project#4676, I implemented the possibility to use the code generation
tooling for the ACTS code generation in an offline environment by
creating a single virtual environment and reusing it across multiple
custom targets. While this works naively, it introduces a race
condition in which multiple threads modify the same virtual environment
at the same time. In order to resolve this problem, I changed the build
system to use a separate virtual environment for every code generation
target.
@github-actions github-actions bot added this to the next milestone Oct 14, 2025
@github-actions github-actions bot added the Infrastructure Changes to build tools, continous integration, ... label Oct 14, 2025
Copy link
Contributor

github-actions bot commented Oct 14, 2025

📊: Physics performance monitoring for 94197b0

Full contents

physmon summary

❗️: Downstream build failure

  • eic-shell (cc @acts-project/epic-contacts)

@stephenswat
Copy link
Member Author

Unfortunately this will need a bit of follow-up work still, as I had misunderstood the core problem.

@stephenswat stephenswat marked this pull request as draft October 14, 2025 12:48
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Infrastructure Changes to build tools, continous integration, ...

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants