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

Fix FLAML installation problems, support version >=2 #626

Merged
merged 1 commit into from
Jun 25, 2024
Merged

Conversation

PGijsbers
Copy link
Collaborator

FLAML was fixed to <2, and would install an incompatible xgboost version. This patch makes it so that newer versions of FLAML can be installed. Additionally, when installing an older version a compatible version of xgboost is installed.
Finally, it adds a definition of flaml:latest in line with the other framework definitions.

Closes #623, #408.

@qingyun-wu as far as I can tell, no changes to the exec.py script are necessary. The simple test cases pass.

FLAML was fixed to <2, and would install an incompatible xgboost
version. This patch makes it so that newer versions of FLAML
can be installed. Additionally, when installing an older version
a compatible version of xgboost is installed.
Finally, it adds a definition of flaml:latest in line with the
other framework definitions.
@PGijsbers PGijsbers added bug Something isn't working framework For issues with frameworks in the current benchmark labels Jun 13, 2024
@PGijsbers
Copy link
Collaborator Author

Merging this since I would like the issues to be resolved and at this point it is not clear if we will get the framework authors to chime in.

@PGijsbers PGijsbers merged commit 077200e into master Jun 25, 2024
8 of 35 checks passed
@PGijsbers PGijsbers deleted the fix/flaml branch June 25, 2024 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working framework For issues with frameworks in the current benchmark
Projects
None yet
Development

Successfully merging this pull request may close these issues.

'NoResultError' raised by FLAML Framework During Benchmark Execution
1 participant