Add integration tests for the file provider#4510
Conversation
b8f1dbe to
f6ca434
Compare
5e1ce42 to
2b3099a
Compare
f6ca434 to
3a9909b
Compare
2b3099a to
a64b81f
Compare
|
Note: To be merged only after : #4449 |
a64b81f to
d41630e
Compare
bb6f77a to
c5bfd62
Compare
Can you keep the older one that failed. A failing test is very valuable for investigation and designing how to handle the NVR parsing. If you have a simpler case that you could produce a similar failure, that would also be good to have. |
What about rather isolating the minimal reproducer (e.g. in a separate pull request) not to block this one? |
Yes, for sure. I mean keeping the older one anywhere, issue, notes, anything. Just not to loose the test case that we stumbled upon. |
psss
left a comment
There was a problem hiding this comment.
Looks good. Just two suggestions.
Created #4549 for a minimal reproducer. So we do not loose the old test. |
LecrisUT
left a comment
There was a problem hiding this comment.
Looks ok to me, but would prefer if we can avoid some duplication.
09a45e8 to
81c0444
Compare
psss
left a comment
There was a problem hiding this comment.
Thanks for the changes, now looks good.
Small hint for the commit summaries:
address review comment
address comments from code review
Choosing a few words describing the actual change helps to
identify what was fixed where and speeds up the review.
|
Tests are actually green. Failures are known eln container issue: Ready for merging. |
81c0444 to
f168f82
Compare
f168f82 to
f3f0713
Compare
|
/packit build |
f3f0713 to
98c0244
Compare
|
/packit build |
2 similar comments
|
/packit build |
|
/packit build |
98c0244 to
cf86708
Compare
Pull Request Checklist
Related to #4420.