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

CI 'tests-with-optuna-master' failing due to botorch installation issue #685

Open
toshihikoyanase opened this issue Nov 8, 2023 · 2 comments
Labels
needs-discussion Issue/PR which needs discussion. no-stale Exempt from stale bot

Comments

@toshihikoyanase
Copy link
Member

Description

The CI job tests-with-optuna-master has been consistently failing for the past two weeks. The failures are occurring during the environment setup phase, specifically at the step where botorch is being installed.

Possible Cause

It appears that the CI environment has been automatically updating to the latest Python version, which has recently changed from 3.11 to 3.12. Up until three weeks ago, the tests were running successfully on Python 3.11.

Proposed Hotfix

As a temporary measure to restore the CI to a passing state, we propose pinning the Python version to 3.11 instead of using the latest version. This would be a hotfix and we would need to investigate a more permanent solution to ensure compatibility with future Python versions.

How to Reproduce

See https://github.com/optuna/optuna-dashboard/actions/workflows/python-tests.yml

Python version

3.12

Optuna version

The current master

optuna-dashboard version or git revision

The feature branches corresponding to the PRs

Web browser

N/A

@toshihikoyanase toshihikoyanase added the needs-discussion Issue/PR which needs discussion. label Nov 8, 2023
Copy link

github-actions bot commented Jan 7, 2024

This issue has not seen any recent activity.

@github-actions github-actions bot added the stale for stale bot label Jan 7, 2024
Copy link

This issue was closed automatically because it had not seen any recent activity. If you want to discuss it, you can reopen it freely.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 15, 2024
@keisuke-umezawa keisuke-umezawa added the no-stale Exempt from stale bot label Jan 16, 2024
@github-actions github-actions bot removed the stale for stale bot label Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-discussion Issue/PR which needs discussion. no-stale Exempt from stale bot
Projects
None yet
Development

No branches or pull requests

2 participants