-
Notifications
You must be signed in to change notification settings - Fork 274
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
Performance-ci centos tests failing in BDN #2496
Comments
@adamsitnik @naricc Have y'all seen an error like this before with BDN? Here is a log with the error: https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-performance-refs-heads-main-367830c2c6914864b5/Partition0/1/console.f1d1238a.log?helixlogtype=result |
Hi @LoopedBard3 ! @MichalStrehovsky has recently fixed this issue with dotnet/BenchmarkDotNet#2020 I've just fixed a recent breaking change: dotnet/BenchmarkDotNet#2045 To fix these builds we need is to upload 0.13.1.1818 to our internal feed and update BDN version in perf repo. Could you please do that? BTW BenchmarkDotNet has recently updated all it's dependencies like TraceEvent, ClrMd and Iced. Some of them might not be in our internal feed(s) yet and you might need to upload them as well. |
Taking a look! |
It looks like there is a new 0.13.1.18.19 version, any reason not to take that one? |
0.13.1.1820 should have my fix. Can we try with that one? |
@MichalStrehovsky I've verified that your fix has solved this problem in #2534, but a new one popped out: dotnet/roslyn#62864 @LoopedBard3 could you please update to |
If it's blocking, downgrading the Roslyn used to build this repo to a build from 2 weeks ago would work around. |
Updated to 0.13.1.1823 in the #2532 PR. |
Looks like the BDN changes are running properly, but there are some tests that are unsupported:
If y'all see something immediately obvious as to why this error was hit (pertaining to what isn't supported, not that something is not supported), please respond. |
It's the issue Adam wrote about above |
It appears that the performance-ci tests for centos are now succeeding on main after merging #2532. Closing issue. |
CentOS runs on the performance-ci are failing due to a type initializer exception. This can be seen in the pipeline here https://dev.azure.com/dnceng/public/_build/results?buildId=1838682&view=logs&jobId=c691a557-b8b7-5576-3a35-6adbad78c2b5, the full error is as follows:
The text was updated successfully, but these errors were encountered: