• Sebastien Robin's avatar
    simulation: solve random solving issues in a cluster environment · 924f20fa
    Sebastien Robin authored
    Before, when solving a solver, parsing sub objects of solver_process was done directly synchronously
    in solver_workflow. And we had the case where you have parallel transactions solving a solver,
    each of theses transactions see remaining solver not in solved state, but once all transaction are
    finished, all solver are solved. This could lead to the case where solver_process is never moved
    to succeeded. Instead of using serialize (which may lead to conflicts), just use activities in queue
    with a serialization tag.
    924f20fa
Name
Last commit
Last update
bt5 Loading commit data...
erp5 Loading commit data...
product Loading commit data...
scalability_test Loading commit data...
slapos Loading commit data...
tests Loading commit data...
.gitignore Loading commit data...
CHANGES.erp5.util.txt Loading commit data...
MANIFEST.in Loading commit data...
Products Loading commit data...
README.erp5.util.txt Loading commit data...
setup.py Loading commit data...