Skip to content
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

Erroneous Reno in tests #678

Closed
prakharb10 opened this issue Sep 15, 2022 · 3 comments · Fixed by #691
Closed

Erroneous Reno in tests #678

prakharb10 opened this issue Sep 15, 2022 · 3 comments · Fixed by #691
Labels
bug Something isn't working

Comments

@prakharb10
Copy link
Contributor

Information

  • retworkx version: 0.11.0
  • Python version: 3.9.6
  • Rust version: 1.63.0
  • Operating system: macOS 12.5.1

What is the current behavior?

There's a reno placed in the test directories at - https://github.com/Qiskit/rustworkx/blob/main/tests/rustworkx_tests/generators/releasenotes/notes/d-1-heavy-hex-e2e44861dc75009a.yaml

I'm not sure, but I think this is erroneous.

What is the expected behavior?

Reno should be placed in the releasenotes directory.

@prakharb10 prakharb10 added the bug Something isn't working label Sep 15, 2022
@mtreinish
Copy link
Member

This is a good catch. We should fix this, the complexity is that this was included in a release already which means if we simply git mv the file to releasenotes.notes reno wiill treat this as part of the next release instead of the previous one. I think to fix this we should copy the contents of the release note included in the previous release like: https://github.com/Qiskit/rustworkx/blob/main/releasenotes/notes/0.11/prepare-0.11-af688e532712c830.yaml and remove the stray file. Then when we build release notes the next time it will include the contents in the proper place.

@prakharb10
Copy link
Contributor Author

I think I understand @mtreinish. I'll try to make a PR with the minor fix.
What about something similar to Qiskit/qiskit#8320 in the repo to prevent this in the future?

@mtreinish
Copy link
Member

Yeah adding the validation job is a good idea, that will prevent this in the future. (and since I'm apparently the typical cause of these issues it'll be good to ensure more discipline on my part)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants