-
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
[TEST] Triggering the ADO tests #1572
Conversation
|
@anargyri in addition, some of the the Github action tests are breaking. For example, the GPU one fails because numba is not detecting a GPU. FYI @laserprec any idea what could be happening? |
There is no cuda 11 installed on the GitHub hosts. I will add new hosts that have cuda 11. |
I think I fixed it with the last PR. Tests are passing here https://dev.azure.com/best-practices/recommenders/_settings/agentqueues?queueId=93&view=jobs |
In a couple of hours we can also check if the badge goes green. |
There is a warning in https://dev.azure.com/best-practices/recommenders/_build/results?buildId=54454&jobId=a2bd9722-611a-5a1a-49b7-b5d4cc326141&view=results about status of runs not being reported. "Failed to post status to GitHub for repository microsoft/recommenders with error: "Not Found". Verify that the GitHub credentials are still valid on the service connection. For OAuth connections, verify that Azure Pipelines is granted access to the repository's organization https://go.microsoft.com/fwlink/?linkid=2019209" The link takes me to the OAuth allowed apps. I don't see Azure Pipelines though. What do you see at this link? |
ADO tests have altogether disappeared from the checks. |
this is weird and annoying. Maybe we can wait until Pradnyesh finish the AzureML tests and remove all this altogether? |
closing this, because it was an old test |
Description
This is a test to understand why the ADO tests in the PR #1565 are not being triggered
Related Issues
Checklist:
staging branch
and not tomain branch
.