Skip to content

Make deterministic the default#1262

Open
StewMH wants to merge 4 commits intoacts-project:mainfrom
StewMH:deterministic
Open

Make deterministic the default#1262
StewMH wants to merge 4 commits intoacts-project:mainfrom
StewMH:deterministic

Conversation

@StewMH
Copy link
Copy Markdown
Contributor

@StewMH StewMH commented Feb 19, 2026

Probably a less surprising default

@StewMH
Copy link
Copy Markdown
Contributor Author

StewMH commented Feb 19, 2026

Wasn't sure if profile.py needed to change as well?

Copy link
Copy Markdown
Member

@krasznaa krasznaa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The C++ code is definitely good this way. @stephenswat will have to have a look at the Python code. Since as I understand it, the code in this repository is just a copy of what he actually uses to run our benchmarks. (I.e. he'll need to pull this update to his copy.)

"Commit is not a child of %s; event order is random",
DETERMINISTIC_ORDER_COMMIT[:8],
)
profile_args.append("--deterministic=0")
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't add this here; this will cause the code to issue an unknown flag to older commits which do not know how to handle that flag. Simply remove the flag from the positive half of the if clause.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a matter of fact, please create two commits: put all the C++ changes in one, then record the commit hash of that commit into this if-else clause. That will be the most robust solution.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stephenswat, could you have a look?

@stephenswat
Copy link
Copy Markdown
Member

Since as I understand it, the code in this repository is just a copy of what he actually uses to run our benchmarks. (I.e. he'll need to pull this update to his copy.)

Actually all the CI jobs use the code from the repository directly, so this should be fine. 🙂

@sonarqubecloud
Copy link
Copy Markdown

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

Successfully merging this pull request may close these issues.

3 participants