Skip to content

Make TFORMx keyword check more flexible - #4653

Merged
astrofrog merged 1 commit into
astropy:masterfrom
olebole:fix_compression_TFORMx_test
Jun 3, 2016
Merged

astrofrog merged 1 commit into
astropy:masterfrom
olebole:fix_compression_TFORMx_test

Conversation

@olebole

@olebole olebole commented Mar 1, 2016

Copy link
Copy Markdown
Member

The maximal column length for compressed data in cfitsio changed between version 3370 and 3380. This patch replaces the check with a specific length by a general check of the correct syntax of the keywords.

This fixes #4646, if @embray raises the green flag.

@olebole
olebole force-pushed the fix_compression_TFORMx_test branch from 8561187 to e6e70d5 Compare March 1, 2016 13:26
@pllim pllim added the io.fits label Mar 1, 2016
@hamogu

hamogu commented Jun 2, 2016

Copy link
Copy Markdown
Member

@pllim @embray : Looking through open PRs. Any comments on this one?

@olebole: I think it needs a changelog entry, but I'm not sure if it will still make it into 1.2 or not.

@olebole

olebole commented Jun 2, 2016

Copy link
Copy Markdown
Member Author

According to @embray's comment, a changelog entry is not needed. I can create one, however, if you still think it is better.

@hamogu

hamogu commented Jun 2, 2016

Copy link
Copy Markdown
Member

Clearly @embray knows that better than I do. I was just trying to go through open PRs with green tests that look as if someone with commit rights just forgot to merge them.

@pllim

pllim commented Jun 2, 2016 •

Copy link
Copy Markdown
Member

At this point, probably not 1.2, but maybe 1.2.x? @astrofrog , what do you think?

@astrofrog

Copy link
Copy Markdown
Member

This should be included in 1.2.0 if possible, since it's just a bug fix.

@olebole - can you add a changelog entry in the 1.2 section?

The maximal column length for compressed data in cfitsio changed between
version 3370 and 3380. This patch replaces the check with a specific length by
a general check of the correct syntax of the keywords.
@olebole
olebole force-pushed the fix_compression_TFORMx_test branch from e6e70d5 to 8a4e41c Compare June 2, 2016 19:51
@olebole

olebole commented Jun 2, 2016

Copy link
Copy Markdown
Member Author

I added one, however I start to feel a bit confused on when a changelog entry is needed.

@astrofrog

Copy link
Copy Markdown
Member

@olebole - a general rule of thumb is, if it fixes an issue with previous released versions, then include a changelog entry. For things like fixing typos or adding a couple of sentences in the documentation, we ususally don't do it though. But here it actually fixes a bug that caused a test to fail in certain circumstances, so to me that's worth a changelog entry.

@astrofrog
astrofrog merged commit 09e603c into astropy:master Jun 3, 2016
@astrobot

astrobot commented Jun 3, 2016

Copy link
Copy Markdown

@astrofrog - thanks for merging this! However, I noticed the following issue with this pull request:

  • Changelog entry not present (or pull request number missing) and neither the Affects-dev nor the no-changelog-entry-needed label are set

Would it be possible to fix this? Thanks!

This is an experimental bot being written by @astrofrog - let me know if the message above is incorrect!

@olebole

olebole commented Jun 3, 2016

Copy link
Copy Markdown
Member Author

@astrofrog is that my fault or did the bot just not recognise the change in CHANGES.rst?

@pllim

pllim commented Jun 3, 2016 •

Copy link
Copy Markdown
Member

The bot demands the number of this PR, not the issue.

@astrofrog

Copy link
Copy Markdown
Member

@olebole - don't worry about this, we're testing out some new rules :) I'll fix it.

@pllim - note that you can still also mention the original issue (and that's a good idea) in addition to the PR number.

astrofrog added a commit that referenced this pull request Jun 3, 2016
Make TFORMx keyword check more flexible
Comment thread CHANGES.rst
- ``astropy.io.fits``

- Made TFORMx keyword check more flexible in test of compressed images to
enable copatibility of the test with cfitsio 3.380. [#4646]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Typically don't put changes to tests in the changelog.

@embray

embray commented Jun 8, 2016

Copy link
Copy Markdown
Member

@astrobot @astrofrog I think changes that just fix a test in order it to pass (in other words, no actual behavior was changed in any significant way) there shouldn't be a changelog entry.

@embray

embray commented Jun 8, 2016

Copy link
Copy Markdown
Member

Maybe there should be a separate category like "Bug-in-test"

@olebole
olebole deleted the fix_compression_TFORMx_test branch June 16, 2016 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

test_compression_column_tforms failure with cfitsio 3.380

6 participants