-
Notifications
You must be signed in to change notification settings - Fork 2
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
Fixed issue with dryrun option that caused hanging #30
Conversation
Fixed an issue with the dryrun option that would cause xdd to hang whenever the option was enabled. The issue lied in src/client/results_manager.c, as it was stuck waiting in a barrier for the other threads to also enter the barrier, which they would never do as the other threads have already exited. Also added a test to ensure that the dryrun option functions correctly. Signed-off-by: MigeljanImeri <ImeriMigel@gmail.com>
748d0c3
to
301d8ea
Compare
@MigeljanImeri I am not sure what is going on here, but this command still hangs: |
Never mind, I was a moron and ran the wrong XDD binary. This looks good and sorry for the confusion on my end. |
Fixed an issue with the dryrun option that would cause xdd to hang whenever the option was enabled. The issue lied in src/client/results_manager.c, as it was stuck waiting in a barrier for the other threads to also enter the barrier, which they would never do as the other threads have already exited. Also added a test to ensure that the dryrun option functions correctly. Signed-off-by: MigeljanImeri <ImeriMigel@gmail.com> Co-authored-by: MigeljanImeri <ImeriMigel@gmail.com>
Fixed an issue with the dryrun option that would cause xdd to hang whenever the option was enabled. The issue lied in src/client/results_manager.c, as it was stuck waiting in a barrier for the other threads to also enter the barrier, which they would never do as the other threads have already exited.
Also added a test to ensure that the dryrun option functions correctly.