Skip to content

ENH: Use appropriate message when reporting TCK file attribute error #1422

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jhlegarreta
Copy link
Contributor

Use appropriate message when reporting file attribute error in TCK: the previous message was mistakenly reporting the non-existence of the file attribute, which indeed has to exist to be able to do the hdr['file'] without getting a KeyError. This patch set uses the message that was not being used when the check was not being successful.

Copy link

codecov bot commented Jul 5, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.34%. Comparing base (b5ecf48) to head (9805f6e).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1422   +/-   ##
=======================================
  Coverage   95.34%   95.34%           
=======================================
  Files         209      209           
  Lines       29780    29780           
  Branches     3357     3357           
=======================================
  Hits        28393    28393           
  Misses        948      948           
  Partials      439      439           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Use appropriate message when reporting `file` attribute error in TCK:
the previous message was mistakenly reporting the non-existence of the
`file` attribute, which indeed has to exist to be able to do the
`hdr['file']` without getting a `KeyError`. This patch set uses the
message that was not being used when the check was not being successful.
@jhlegarreta jhlegarreta force-pushed the UseAppropriateMsgInTckError branch from 3993b97 to 9805f6e Compare July 5, 2025 21:40
@jhlegarreta
Copy link
Contributor Author

jhlegarreta commented Jul 5, 2025

Style errors predated this PR. Addressed in PR #1423.
Type checking errors predated this PR. Addressed in PR #1424.

@jhlegarreta
Copy link
Contributor Author

@effigies this is ready to be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant