-
Notifications
You must be signed in to change notification settings - Fork 5.4k
Open
Labels
JitStressCLR JIT issues involving JIT internal stress modesCLR JIT issues involving JIT internal stress modesarea-Tracing-coreclrblocking-clean-ci-optionalBlocking optional rolling runsBlocking optional rolling runsuntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner
Description
Failed in: runtime-coreclr jitstressregs 20260308.1
Failed tests:
coreclr linux arm64 Checked jitstressregs2 @ AzureLinux.3.Arm64.Open
- tracing/userevents/custommetadata/custommetadata/custommetadata.cmd
Error message:
The trace did not contain the expected CustomMetadata event from tracee PID 3086.
Trace file `/datadisks/disk1/work/C6200AA9/t/tmpsbVYNs.nettrace` does not contain expected events.
Return code: 1
Raw output file: /datadisks/disk1/work/C6200AA9/w/A9DD0970/uploads/userevents/custommetadata/custommetadata/output.txt
Raw output:
BEGIN EXECUTION
/datadisks/disk1/work/C6200AA9/p/corerun -p System.Reflection.Metadata.MetadataUpdater.IsSupported=false -p System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true custommetadata.dll ''
Starting record-trace: sudo -n /datadisks/disk1/work/C6200AA9/w/A9DD0970/e/tracing/userevents/common/userevents_common/record-trace --script-file /datadisks/disk1/work/C6200AA9/w/A9DD0970/e/tracing/userevents/custommetadata/custommetadata/custommetadata.script --out /datadisks/disk1/work/C6200AA9/t/tmpsbVYNs.nettrace --log-path /datadisks/disk1/work/C6200AA9/t/tmpsbVYNs.log
record-trace started with PID: 3080
Delaying tracee startup 300ms for record-trace setup...
Starting tracee process: /datadisks/disk1/work/C6200AA9/p/corerun /datadisks/disk1/work/C6200AA9/w/A9DD0970/e/tracing/userevents/custommetadata/custommetadata/custommetadata.dll tracee
Tracee process started with PID: 3086
Waiting for tracee process to exit...
[tracee][stdout] Tracee waiting for EventSource to be enabled via IPC...
[record-trace][stdout] Recording started. Press CTRL+C to stop.
Tracee process did not exit within the 60000ms timeout, killing it.
Stopping record-trace with SIGINT.
Waiting for record-trace to exit...
[record-trace][stdout] Recording stopped.
[record-trace][stdout] Resolving symbols.
[record-trace][stdout] Finished recording trace.
[record-trace][stdout] Trace written to /datadisks/disk1/work/C6200AA9/t/tmpsbVYNs.nettrace
Ignored 7354 events from processes other than tracee (PID 3086).
Uploading artifact to Helix work item directory: /datadisks/disk1/work/C6200AA9/w/A9DD0970/uploads/custommetadata.nettrace
Uploading artifact to Helix work item directory: /datadisks/disk1/work/C6200AA9/w/A9DD0970/uploads/custommetadata.log
Expected: 100
Actual: 255
END EXECUTION - FAILED
Test Harness Exitcode is : 1
To run the test:
Set up CORE_ROOT and run.
> /datadisks/disk1/work/C6200AA9/w/A9DD0970/e/tracing/tracing/../userevents/custommetadata/custommetadata/custommetadata.sh
Stack trace:
at Xunit.Assert.True(Nullable`1 condition, String userMessage) in /_/src/arcade/src/Microsoft.DotNet.XUnitAssert/src/BooleanAsserts.cs:line 141
at Program.<<Main>$>g__TestExecutor40|0_41(StreamWriter tempLogSw, StreamWriter statsCsvSw, <>c__DisplayClass0_0&)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
JitStressCLR JIT issues involving JIT internal stress modesCLR JIT issues involving JIT internal stress modesarea-Tracing-coreclrblocking-clean-ci-optionalBlocking optional rolling runsBlocking optional rolling runsuntriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner