Closed suzhoum closed 11 months ago
Thanks for the report. It is related to the server issues. our infrastructure is up and running again so there is no error 503, but we have this problem now. This has to be fixed serverside, I forwarded the report/request. Your report of problems starting last week matches up with the server problems at OpenML.
Thanks for your response @PGijsbers! One thing that I'm unsure about is that why AMLB works on my dev machine (EC2), but not in a docker. Is there any workaround at the moment for docker?
Did you upgrade your dev machine to OpenML Python 0.14.1? Your docker will be at 0.13.1. Also server issues are clearing up so hopefully both work soon automagically regardless :)
I was actually using 0.13.1 on my dev machine as I created a new virtual env for it and installed the default packages from requirements.txt
.
Did you run the command in your local environment a while back? Maybe somehow the OpenML cache is not shared with the docker container, and the local environment loads a correct cached file but docker downloads a new corrupted file. I can try to reproduce it later this week, though there is a chance server issues are resolved before it.
Oh that totally makes sense now. Yes I have been running the benchmark in my local environment since a few months ago, and the cache should still be available, while the container is built fresh.
OpenML server issues should mostly be gone now. I just ran python3 automlbenchmark/runbenchmark.py AutoGluon:stable small test -t vehicle -f 0
locally after clearing my cache (rm -rf ~/.openml/org/openml/www/datasets/54
) and it completed successfully:
Processing results for autogluon.small.test.local.20230730T142453
Summing up scores for current run:
id task fold framework constraint result metric duration seed
openml.org/t/53 vehicle 0 AutoGluon test -0.404008 neg_logloss 69.0 1666932321
Can you see if the problem still occurs?
It's working fine now!
I need to clone automlbenchmark in my container and run the benchmarks within, it's been running fine until just last week. I wonder what has changed that caused the git errors. It errors out when running
This is running fine:
The Dockerfile is simple:
In
entrypoint.sh
: