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.

Sign up for GitHub

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

Jump to bottom

Handle incorrect release provided while fetching builds based on release #96

Open
KeerthanaAP opened this issue Jan 10, 2025 · 0 comments · May be fixed by #98
Open

Handle incorrect release provided while fetching builds based on release #96

KeerthanaAP opened this issue Jan 10, 2025 · 0 comments · May be fixed by #98
Assignees
@KeerthanaAP

Comments

@KeerthanaAP
Copy link
Collaborator 

Enter the option: 7
Enter the release: 4.14.44
Enter the next release (provide latest if no next release): 4.14.45
Invalid date format
Traceback (most recent call last):
  File "/Users/keerthanaarumugam/Documents/Projects/Monitoring/ci-monitoring-automation/CI_JobHistory.py", line 379, in <module>
    main()
  File "/Users/keerthanaarumugam/Documents/Projects/Monitoring/ci-monitoring-automation/CI_JobHistory.py", line 297, in main
    start_date,end_date = get_release_date()
TypeError: cannot unpack non-iterable NoneType object

Here the next release should be latest but when we provide an incorrect release version it needs to be handled properly in the code.
@KeerthanaAP KeerthanaAP self-assigned this Jan 10, 2025
@KeerthanaAP KeerthanaAP linked a pull request Jan 24, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KeerthanaAP KeerthanaAP

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added check to handle invalid release. KeerthanaAP/ci-monitoring-automation
1 participant
@KeerthanaAP