BlueBrain
Myers diff algorithm for unit tests
This is a small new feature for a bit of convenience. This PR adds a proper diff implementation that can be invoked when a unit test fails. Instead of outputting the the raw generated strings and painstakingly comparing them, we can now simply diff them and print formatted output.
For now just one test case was updated as an example for initial feedback.
Logfiles from GitLab pipeline #194925 (:no_entry:) have been uploaded here!
Status and direct links:
- :white_check_mark: spack_setup
- :white_check_mark: build:intel
- :white_check_mark: build:nvhpc
- :white_check_mark: test:intel
- :white_check_mark: test:nvhpc
I'd propose thorough (unit-) testing. ~To me it looked like you intentionally broke the tests to show how it would fail. However the tests pass and don't show what this would look like when something fails.~
Logfiles from GitLab pipeline #198072 (:no_entry:) have been uploaded here!
Status and direct links:
- :white_check_mark: spack_setup
- :white_check_mark: build:intel
- :white_check_mark: build:nvhpc
- :white_check_mark: test:intel
- :white_check_mark: test:nvhpc
Logfiles from GitLab pipeline #198084 (:no_entry:) have been uploaded here!
Status and direct links:
- :white_check_mark: spack_setup
- :white_check_mark: build:intel
- :white_check_mark: build:nvhpc
- :white_check_mark: test:intel
- :white_check_mark: test:nvhpc
Logfiles from GitLab pipeline #212074 (:no_entry:) have been uploaded here!
Status and direct links:
- :white_check_mark: spack_setup
- :no_entry: build:intel
- :no_entry: build:nvhpc
- :fast_forward: test:intel
- :fast_forward: test:nvhpc
I'll close this. As discussed, it's not very high priority and unless someone has interest and finds the time this can just stay in a branch.