🔒 🤖 CI Update lock files for main CI build(s) 🔒 🤖 #30636
Conversation
5687956 to
938cf08
Compare
|
looks like the failure comes from openml being down for some time. |
|
The failure is due to openml being down. I'll retry later when it's up. |
|
I suppose that we do not experience the problem on the other CI builds because of the CI cache key that is derived from the lock files? If so that is a very nice side effect of using lock files :) /cc @lesteve. |
|
I don't think lock-files are involved, it is more that most builds don't actually download data from OpenML 😉. Even CircleCI builds won't download data from OpenML unless you use FYI, there is a bit of info of the OpenML status on their Slack. Last update was yesterday (January 15th):
|
938cf08 to
1eac4b4
Compare
|
We now also get HTTP 403 errors when calling |
|
This problem is probably caused by an anti-DOS mechanism of the figshare hosting platforms with a denylist on a range of IP addresses from cloud hosted machines sometime used by our CI workers. We experienced a similar problem in the past: |
I had seen the doctest failures and just thought "oh well another failure due to OpenML" but indeed it's not fetched from OpenML 😅 ... Whatever is easier:
|
|
Maybe I am over-cautious but I would not merge this without making sure that the full doc build works, which we can not do for now since OpenML is still not fully functional. Maybe I am missing something or maybe you ran the doc build locally? I have disabled auto-merge for now. |
|
OK I now had a look at the diff and it seems like it's very minimal for the doc builds so I guess YOLO while OpenML is still problematic and we still can 🤠 |
Update lock files.
Note
If the CI tasks fail, create a new branch based on this PR and add the required fixes to that branch.