-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove unnecessary field #3137
Remove unnecessary field #3137
Conversation
Looks like there was a bug hiding in there as well... |
I'm very puzzled why it's only failing on some of the test runs. |
I think there are some 30+ new lines not parsed before!
|
Not all jobs run all the tests, e.g. some unit tests or NLS tests are skipped on some... |
I mean, there's recursion going on. That's probably why it's a member of the class. |
locally these are the new lines:
how strange... edit: analyzing further I see in the reference
but no corresponding Exif.Photo.ColorSpace entry. With this PR it's
is this a bugfix? |
388344b
to
813af22
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3137 +/- ##
==========================================
+ Coverage 64.65% 64.71% +0.06%
==========================================
Files 104 104
Lines 22167 22164 -3
Branches 10852 10843 -9
==========================================
+ Hits 14331 14344 +13
+ Misses 5596 5590 -6
+ Partials 2240 2230 -10 ☔ View full report in Codecov by Sentry. |
Looks like it. Members |
I need to do a bit more investigation to understand why this changes the results. At least it's not non-deterministic, which is what it looked like to me when only half the test runs failed. I suspect it's something like it's changed the order of the elements in the components list, so when it searches for the first match it's getting a different answer. |
Well, the test reference output was wrong to begin with - looks like we were actually deleting stuff (existing data was no longer in the output) after all the "set" actions, so this was definitely a bug... |
I found the difference. Previously, this code was never executed: Lines 568 to 571 in d7ac558
It wasn't called because After this PR, the test calls that code exactly once. It creates a new |
Now that I look at this, why is m_ a member of the class? It's only used in this function
tests succeed. |
@mergify backport 0.28.x |
✅ Backports have been created
|
Remove
CiffDirectory::cc_
. It's a raw pointer, so it's ownership is unclear. There also doesn't seem to be any reason to store it in the object.