-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[BUG] Test failing Service invocation timed out #2147
Comments
Perhaps we should give it a bit more time until timeout in case the machine is taking a while to start? |
I run it again and got a slightly different error: https://github.com/recommenders-team/recommenders/actions/runs/10412300049/job/28895746683 We need to check whether the VMs can be accessed.
|
Added a new cluster, with the same details as before (Standard_F32s_v2 (32 cores, 64 GB RAM, 256 GB disk, low priority, $0.27/hr per node), but didn't work either https://github.com/recommenders-team/recommenders/actions/runs/10454246686 If I try to list the jobs in that cluster I get an error:
|
Created a new cluster with dedicated VMs: Standard_F32s_v2 (32 cores, 64 GB RAM, 256 GB disk), dedicated, $1.35/hr per node Same error as in #2148 |
Pinned |
@miguelgfierro Could you check if there is a experiment named |
For the record, the last working test was on August 11th: https://github.com/recommenders-team/recommenders/actions/runs/10335388423 |
All tests have passed after I re-run them. It may be the problem of Azure service. |
I'm running all the tests again to check:
Some are failing, this is very weird, there is no difference in the AzureML code between staging and main. The error is the same:
They have created an ICM ticket, it seems there are issues in US East region. |
Now
|
let me merge #2145 and see if everything is green |
It seems everything is green except the CPU nightly It seems there is an error with MIND:
It is not very clear what it is. Something weird that happened is that the logs of the tests were not fully written:
It should get pass 29% and write the errors. |
This has been fixed |
Description
The VMs for the tests are not even starting:
In which platform does it happen?
How do we replicate the issue?
See example: https://github.com/recommenders-team/recommenders/actions/runs/10406895552/job/28821110978
Expected behavior (i.e. solution)
Willingness to contribute
Other Comments
FYI @SimonYansenZhao
The text was updated successfully, but these errors were encountered: