-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[wasm] Tracking aot failures, not meant to be merged #52004
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
We should disable all the non-wasm builds here. |
We should only run wasm aot lane here to save the resources. |
#52265 will fix the EAT error |
/azp run runtime,runtime-staging |
Azure Pipelines successfully started running 2 pipeline(s). |
/azp run runtime |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime |
Azure Pipelines successfully started running 1 pipeline(s). |
@radical it looks like several of the EAT lans have a 0 exit code but no failures? |
which ones? I didn't see any in EAT, or AOT. |
Sorry, I meant in the data explorer reports |
/azp run runtime |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run runtime |
Pull request contains merge conflicts. |
/azp run runtime |
Azure Pipelines successfully started running 1 pipeline(s). |
Draft Pull Request was automatically closed for inactivity. Please let us know if you'd like to reopen it. |
/azp run runtime |
Pull request contains merge conflicts. |
/azp run runtime |
Pull request contains merge conflicts. |
Draft Pull Request was automatically closed for inactivity. Please let us know if you'd like to reopen it. |
main
will be merged here regularly