Skip to content
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

Closed
wants to merge 21 commits into from

Conversation

radical
Copy link
Member

@radical radical commented Apr 28, 2021

  • this re-enables any tests that were disabled due to aot only failures
  • This will never be merged
  • It's only to track aot test failures
  • main will be merged here regularly

@dotnet-issue-labeler
Copy link

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.

@radical
Copy link
Member Author

radical commented Apr 28, 2021

@radical radical added the arch-wasm WebAssembly architecture label Apr 28, 2021
@ghost
Copy link

ghost commented Apr 28, 2021

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details
  • this re-enables any tests that were disabled due to aot only failures
  • This will never be merged
  • It's only to track aot test failures
  • main will be merged here regularly
Author: radical
Assignees: -
Labels:

arch-wasm

Milestone: -

@radekdoulik radekdoulik added the NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons) label Apr 28, 2021
@radical
Copy link
Member Author

radical commented Apr 28, 2021

We should disable all the non-wasm builds here.

@fanyang-mono
Copy link
Member

We should disable all the non-wasm builds here.

We should only run wasm aot lane here to save the resources.

@radical
Copy link
Member Author

radical commented May 4, 2021

#52265 will fix the EAT error

@radical
Copy link
Member Author

radical commented Jun 16, 2021

/azp run runtime,runtime-staging

@azure-pipelines
Copy link

Azure Pipelines successfully started running 2 pipeline(s).

@lewing
Copy link
Member

lewing commented Aug 5, 2021

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lewing
Copy link
Member

lewing commented Aug 16, 2021

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lewing
Copy link
Member

lewing commented Aug 16, 2021

@radical it looks like several of the EAT lans have a 0 exit code but no failures?

@radical
Copy link
Member Author

radical commented Aug 16, 2021

@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.

@lewing
Copy link
Member

lewing commented Aug 16, 2021

Sorry, I meant in the data explorer reports

@lewing
Copy link
Member

lewing commented Aug 18, 2021

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@lewing
Copy link
Member

lewing commented Aug 24, 2021

/azp run runtime

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@lewing
Copy link
Member

lewing commented Aug 27, 2021

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@ghost ghost closed this Sep 26, 2021
@ghost
Copy link

ghost commented Sep 26, 2021

Draft Pull Request was automatically closed for inactivity. Please let us know if you'd like to reopen it.

@radical radical reopened this Sep 26, 2021
@lewing
Copy link
Member

lewing commented Oct 28, 2021

/azp run runtime

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@lewing
Copy link
Member

lewing commented Nov 10, 2021

/azp run runtime

@azure-pipelines
Copy link

Pull request contains merge conflicts.

@ghost ghost closed this Dec 10, 2021
@ghost
Copy link

ghost commented Dec 10, 2021

Draft Pull Request was automatically closed for inactivity. Please let us know if you'd like to reopen it.

@ghost ghost locked as resolved and limited conversation to collaborators Jan 10, 2022
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture NO-MERGE The PR is not ready for merge yet (see discussion for detailed reasons)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants