Skip to content

Conversation

am11
Copy link
Member

@am11 am11 commented Jul 8, 2025

No description provided.

@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates that the PR has been added by a community member label Jul 8, 2025
@am11 am11 added the arch-riscv Related to the RISC-V architecture label Jul 8, 2025
@am11 am11 requested review from a team and jkoritzinsky July 8, 2025 20:39
@risc-vv
Copy link

risc-vv commented Jul 8, 2025

@dotnet/samsung Could you please take a look? These changes may be related to riscv64.

@steveisok steveisok requested a review from max-charlamb July 8, 2025 20:42
@am11
Copy link
Member Author

am11 commented Jul 8, 2025

@dotnet/samsung, @filipnavara, FYI. I haven't tested it with dotnet/diagnostics repo (libSOS lldb plugin) yet. But it would be easier to fine tune it once the bulk of change is in. Good thing is that it's an independent component at the moment, future replacement for existing/classic DAC.

@risc-vv
Copy link

risc-vv commented Jul 9, 2025

{CONFIG}-CLR-tests FAILED

buildinfo.json
coreCLR tests failed for unknown reason. Check buildinfo.json or gocd for more details.

RISC-V Release-FX-QEMU: 281132 / 282209 (99.62%)
=======================
      passed: 281132
      failed: 1070
     skipped: 39
      killed: 7
------------------------
 TOTAL tests: 282248
VIRTUAL time: 31h 22min 54s 333ms
   REAL time: 1h 10min 24s 74ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

RISC-V Release-FX-VF2: 380606 / 381279 (99.82%)
=======================
      passed: 380606
      failed: 664
     skipped: 20
      killed: 9
------------------------
 TOTAL tests: 381299
VIRTUAL time: 13h 34min 8s 859ms
   REAL time: 1h 26min 37s 556ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

Build information and commands

GIT: 160881c34e6b2929f2082d6c15d21ae8181a4c1f
CI: d6c9c1ab3a7411819463edc05ded301e89ba586a
REPO: dotnet/runtime
BRANCH: main
CONFIG: Release
LIB_CONFIG: Release

@am11 am11 force-pushed the feature/cdac/riscv64-unwinder branch 2 times, most recently from 62b5ef0 to 51149e9 Compare July 9, 2025 11:51
@risc-vv
Copy link

risc-vv commented Jul 9, 2025

RISC-V Release-CLR-QEMU: 9082 / 9112 (99.67%)
=======================
      passed: 9082
      failed: 2
     skipped: 597
      killed: 28
------------------------
 TOTAL tests: 9709
VIRTUAL time: 37h 24min 32s 497ms
   REAL time: 38min 9s 665ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

Build information and commands

GIT: 51149e9a91ff508c22ffe3817cebbbab7498a6a0
CI: d6c9c1ab3a7411819463edc05ded301e89ba586a
REPO: dotnet/runtime
BRANCH: main
CONFIG: Release
LIB_CONFIG: Release

@risc-vv
Copy link

risc-vv commented Jul 9, 2025

RISC-V Release-FX-QEMU: 283572 / 284668 (99.61%)
=======================
      passed: 283572
      failed: 1086
     skipped: 39
      killed: 10
------------------------
 TOTAL tests: 284707
VIRTUAL time: 33h 25min 43s 223ms
   REAL time: 1h 11min 0s 332ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

Build information and commands

GIT: 51149e9a91ff508c22ffe3817cebbbab7498a6a0
CI: d6c9c1ab3a7411819463edc05ded301e89ba586a
REPO: dotnet/runtime
BRANCH: main
CONFIG: Release
LIB_CONFIG: Release

@risc-vv
Copy link

risc-vv commented Jul 9, 2025

RISC-V Release-CLR-QEMU: 9082 / 9112 (99.67%)
=======================
      passed: 9082
      failed: 2
     skipped: 597
      killed: 28
------------------------
 TOTAL tests: 9709
VIRTUAL time: 37h 27min 31s 435ms
   REAL time: 39min 35s 917ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

Build information and commands

GIT: 51149e9a91ff508c22ffe3817cebbbab7498a6a0
CI: d6c9c1ab3a7411819463edc05ded301e89ba586a
REPO: dotnet/runtime
BRANCH: main
CONFIG: Release
LIB_CONFIG: Release

@risc-vv
Copy link

risc-vv commented Jul 9, 2025

RISC-V Release-CLR-VF2: 9083 / 9113 (99.67%)
=======================
      passed: 9083
      failed: 2
     skipped: 597
      killed: 28
------------------------
 TOTAL tests: 9710
VIRTUAL time: 11h 32min 7s 973ms
   REAL time: 46min 45s 227ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

RISC-V Release-FX-QEMU: 283220 / 284300 (99.62%)
=======================
      passed: 283220
      failed: 1073
     skipped: 39
      killed: 7
------------------------
 TOTAL tests: 284339
VIRTUAL time: 32h 34min 53s 425ms
   REAL time: 1h 12min 0s 380ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

RISC-V Release-FX-VF2: 309598 / 311346 (99.44%)
=======================
      passed: 309598
      failed: 1739
     skipped: 39
      killed: 9
------------------------
 TOTAL tests: 311385
VIRTUAL time: 23h 3min 16s 627ms
   REAL time: 2h 12min 4s 42ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

Build information and commands

GIT: 2f2e22063b0afaa65fa8d33c7170cc9f6f5b5743
CI: d6c9c1ab3a7411819463edc05ded301e89ba586a
REPO: dotnet/runtime
BRANCH: main
CONFIG: Release
LIB_CONFIG: Release

@am11 am11 force-pushed the feature/cdac/riscv64-unwinder branch from 2f2e220 to d436429 Compare July 9, 2025 17:13
Copy link
Member

@max-charlamb max-charlamb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cDAC implementation looks good module comments. I don't have as much insight into the build changes.

Thanks for adding this!

@risc-vv
Copy link

risc-vv commented Jul 9, 2025

RISC-V Release-CLR-VF2: 9083 / 9113 (99.67%)
=======================
      passed: 9083
      failed: 2
     skipped: 597
      killed: 28
------------------------
 TOTAL tests: 9710
VIRTUAL time: 11h 34min 7s 471ms
   REAL time: 46min 57s 341ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

Build information and commands

GIT: 53fad81d5fb4f5059264c51335c7fbe2b716bb1b
CI: d6c9c1ab3a7411819463edc05ded301e89ba586a
REPO: dotnet/runtime
BRANCH: main
CONFIG: Release
LIB_CONFIG: Release

@am11
Copy link
Member Author

am11 commented Jul 9, 2025

/runtime/.dotnet/sdk/10.0.100-preview.6.25315.102/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1047: Assets file '/runtime/artifacts/obj/Mono.Linker/project.assets.json' doesn't have a target for 'net10.0/linux-riscv64'. Ensure that restore has run and that you have included 'net10.0' in the TargetFrameworks for your project. You may also need to include 'linux-riscv64' in your project's RuntimeIdentifiers. [/runtime/src/tools/illink/src/linker/Mono.Linker.csproj]

This NETSDK1047 is being raised intermittently with live linker (sometimes freebsd-x64 bootstrapped fails, other times linux-riscv64 or loongarch64). I found a conversation between @ViktorHofer and @jkoritzinsky #92826 (comment), perhaps removing this global property:

src/native/managed/subproject.props:        <SubprojectProps Include="RuntimeIdentifier" Value="$(TargetRid)" />

may help? I checked Mono.Linker.csproj's project.assets.json generated under obj/ dir, it sometimes have net10.0/linux-loongarch64 (or riscv64 etc.) at the point cDAC is published (when it passes), other times it doesn't have the RID node in that JSON file. Without importing live linker targets, it fails due to the missing PrepareForILLink target. We can hack this target as well. I'm not sure what's the proper way to address it.

@risc-vv
Copy link

risc-vv commented Jul 9, 2025

RISC-V Release-CLR-VF2: 9083 / 9113 (99.67%)
=======================
      passed: 9083
      failed: 2
     skipped: 597
      killed: 28
------------------------
 TOTAL tests: 9710
VIRTUAL time: 11h 12min 45s 59ms
   REAL time: 45min 32s 750ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

RISC-V Release-CLR-QEMU: 9082 / 9112 (99.67%)
=======================
      passed: 9082
      failed: 2
     skipped: 597
      killed: 28
------------------------
 TOTAL tests: 9709
VIRTUAL time: 37h 24min 50s 922ms
   REAL time: 38min 7s 177ms
=======================

report.xml, report.md, failures.xml, testclr_details.tar.zst

Build information and commands

GIT: 66c1fb239626593a5951d1f8b322a3e447216b09
CI: d6c9c1ab3a7411819463edc05ded301e89ba586a
REPO: dotnet/runtime
BRANCH: main
CONFIG: Release
LIB_CONFIG: Release

@risc-vv
Copy link

risc-vv commented Aug 22, 2025

@dotnet/samsung Could you please take a look? These changes may be related to riscv64.

1 similar comment
@risc-vv
Copy link

risc-vv commented Aug 28, 2025

@dotnet/samsung Could you please take a look? These changes may be related to riscv64.

@tomeksowi
Copy link
Member

@dotnet/samsung Could you please take a look? These changes may be related to riscv64.

Sorry for spam, disabled for now

@am11
Copy link
Member Author

am11 commented Aug 30, 2025

@jkoritzinsky I tried a few more things (e.g., setting HasRuntimeOutput=false), but it didn’t help; three out of five builds are still failing. In CI, the failing bootstrap leg varies from run to run (sometimes riscv64, sometimes loongarch64, sometimes freebsd), so it seems to be intermittent rather than tied to a specific bootstrap platform.

If you have other ideas to make Mono.Linker.csproj restore more reliable, please let me know, or feel free to push commits directly to the PR branch.

@am11
Copy link
Member Author

am11 commented Sep 5, 2025

Use the right property name (really wish this was better doc'd

Thanks a lot @jkoritzinsky! Six repeated builds passed (earlier three out of five builds were failing).

Can we test this change in dotnet/dotnet before merging the PR? We saw two issues earlier:

  1. [main] Source code updates from dotnet/runtime dotnet#1392 (comment) P2P ref fails, I think we will need to separate cDAC _inbuild and _published csprojs same as ilc / cg2 to satisfy the matrix.
  2. Punt on cdac transport pack for linux-musl dotnet#1464 something in linux-musl cDAC package fails, most likely linux vs. linux-musl in path but it's a guess since the PR description didn't specify the error it was fixing. Perhaps we can run specific CI leg which failed to find out the details.

@jkoritzinsky
Copy link
Member

@am11 for 1) I would expect that doing the same GlobalPropertiesToRemove trick would work.
for 2) I'm unsure and I'd rather defer that to the cdac folks to figure out when they're shipping if we can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

arch-riscv Related to the RISC-V architecture area-Diagnostics-coreclr community-contribution Indicates that the PR has been added by a community member linkable-framework Issues associated with delivering a linker friendly framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants