Consider commit a62ce64c51da6e0461a5eac3ac76af9e541c56fcgit rev-parse HEAD
a62ce64c51da6e0461a5eac3ac76af9e541c56fc
When i run python test_compare_aurora_vs_archived_emtf.py, the test (which numerically compares synthetic processing results with expected, PASSES.
One commit later, 55e205497fe7012d8c6d52d76bcb1d851e89a0b2
there is exactly one change, which corresponds to opening the file in append mode, and not read mode,
And python test_compare_aurora_vs_archived_emtf.py fails
The change is results is trivial, the question is why should they change at all?
This is weird.
Consider commit
a62ce64c51da6e0461a5eac3ac76af9e541c56fcgit rev-parse HEADWhen i run
python test_compare_aurora_vs_archived_emtf.py, the test (which numerically compares synthetic processing results with expected, PASSES.One commit later,
55e205497fe7012d8c6d52d76bcb1d851e89a0b2there is exactly one change, which corresponds to opening the file in append mode, and not read mode,And
The change is results is trivial, the question is why should they change at all?
python test_compare_aurora_vs_archived_emtf.pyfails