Fix logging in export_history.py, fix Azure and S3 tests #19542
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.
TL;DR Absolute non-issue, really irrelevant fix, just noticed things were wrong while fixing something else.
On line 59 from export_history.py,
actual_uri = _write_to_destination(options.file_sources, os.path.abspath(out_file), destination_uri)
, but_write_to_destination()
yields just the path of the saved file, sodestination_uri != actual_uri
is alwaysTrue
and the print statement always kicks-in.In addition,
write_from()
from test/unit/files/_util.py is wrong in a way such thatassert_can_write_and_read_to_conf()
from the same file should always fail. It went unnoticed just because the tests that use it are skipped by default.How to test the changes?
(Select all options that apply)
License