Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The GMG solver always outputs an additional line in the log.txt and screen output that informs the user about the level of vectorization, even though this is already stated (in less detail) in the ASPECT header. This is slightly annoying, and moreover, because this line is not removed from the test output it causes issues if different testers use different vectorizations (e.g. the Jenkins OSX tester, which creates different output than the Jenkins tester for the
quick_mpi
test if run with GMG).Therefore I propose to remove the extra line, and always output the vectorization information in the header. This looks cleaner and resolves the tester problems in #5211.
Previously the output would look like this:
Now it looks like this (ignore the changed vectorization information, I ran the output above inside the docker container and the one below on my native OS):