-
Notifications
You must be signed in to change notification settings - Fork 272
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 AOT runs not autofiled #2824
Comments
cc @lewing |
I think this is because dotnet/performance is targeting net7.0 still and the workaround we used to make it use the net8 runtimes for wasm was disabled so the tests have just been targeting a stable build of the runtime |
The change that caused the workaround to break things went in on December 9th so without manual work this is going to leave us with a month long (Since December 9th) hole in the net8 runtime data for wasm across some fairly important changes. |
I am doing testing on these changes as we speak. If everything works I will check in the change in the performance repo.
How many big changes and when did they go in? We could go back and run some builds around the major changes that happened so that we can go back and fill in with the correct data going forward. |
@kg which jiterperter commits are most important to have data on? |
Before and after dotnet/runtime#78493 would be a valuable diff to have. |
dotnet/runtime#79302 would be nice check regressions from |
where is the `compliationmode" typo coming from in the labels now? (see #2750) |
This came from a typo that I had about 4 years ago when I was first putting the lab together. Since then, we have never been able to fully purge it from the system, and because of the way that trends are correlated it is challenging to go back and fix old labels. |
Fixed by: #2816 |
It appears that the following check has not been auto-filing correctly:
The run results are showing up in the tables. Investigating the autofile runs to see if they directly failed or if something else is going on.
The text was updated successfully, but these errors were encountered: