Skip to content

TestStl: cleaned up settings usage#7930

Merged
firewave merged 1 commit intodanmar:mainfrom
firewave:teststl
Oct 29, 2025
Merged

TestStl: cleaned up settings usage#7930
firewave merged 1 commit intodanmar:mainfrom
firewave:teststl

Conversation

@firewave
Copy link
Copy Markdown
Collaborator

No description provided.

@sonarqubecloud
Copy link
Copy Markdown

Comment thread test/teststl.cpp
Comment on lines -190 to +192
const Settings settings1 = settingsBuilder(settings).certainty(Certainty::inconclusive, options.inconclusive).cpp(options.cppstandard).build();
const Settings* s = options.s ? options.s : (options.inconclusive ? &settings_i : &settings);
Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

inconclusive is not applied to custom settings but I think that is fine. We could add a sanity check (or overload) to make sure that nothing is supplied with the custom settings - but that applies across all tests and so is out-of-scope for this PR.

@firewave
Copy link
Copy Markdown
Collaborator Author

This saves another 30 seconds to in slow running tests in the CI.

@firewave firewave merged commit 019c37c into danmar:main Oct 29, 2025
55 checks passed
@firewave firewave deleted the teststl branch October 29, 2025 18:20
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.

2 participants