Skip to content

Conversation

@joa-quim
Copy link
Member

Closes #3657

@joa-quim joa-quim requested a review from PaulWessel July 14, 2020 11:01
@joa-quim joa-quim added the backport 6.1 Backport this PR to 6.1 branch label Jul 14, 2020
Copy link
Member

@PaulWessel PaulWessel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming tests still pass.

@joa-quim
Copy link
Member Author

Well, broken is what it was.

@PaulWessel
Copy link
Member

Need to add a test since clearly no test checked this part. COuld you do that?

@seisman
Copy link
Member

seisman commented Jul 14, 2020

We have many failures on Windows recently (#3642), possibly due to this bug.

@PaulWessel
Copy link
Member

Does this raise to the level of a 6.1.1 before the workshop next week?

@seisman
Copy link
Member

seisman commented Jul 14, 2020

Does this raise to the level of a 6.1.1 before the workshop next week?

It looks a new bug introduced after 6.1.0 release. The reasons are:

  1. There are no related failures when we released 6.1.0
  2. You made some changes in PR Let gdal_open know about and apply cache dir #3596, after releasing 6.1.0. Perhaps the bug were introduced in your PR Let gdal_open know about and apply cache dir #3596?

@joa-quim
Copy link
Member Author

Yes, #3596 introduced the bug but lucky of us that it was hold to after 6.1, so we don't need to release a 6.1.1. Just fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport 6.1 Backport this PR to 6.1 branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reading @ with GDAL is broken on Windows

4 participants