Skip to content
This repository was archived by the owner on Jan 23, 2023. It is now read-only.

Add environment variable (COMPlus_EnableDiagnostics) to disable debuggging and profiling#16141

Merged
mikem8361 merged 1 commit into
dotnet:masterfrom
mikem8361:disabledbg
Mar 17, 2018
Merged

Add environment variable (COMPlus_EnableDiagnostics) to disable debuggging and profiling#16141
mikem8361 merged 1 commit into
dotnet:masterfrom
mikem8361:disabledbg

Conversation

@mikem8361
Copy link
Copy Markdown

This reverts commit e998512.

@mikem8361 mikem8361 added the * NO MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) label Feb 1, 2018
@mikem8361 mikem8361 added this to the 2.1.0 milestone Feb 1, 2018
@mikem8361 mikem8361 self-assigned this Feb 1, 2018
@mikem8361 mikem8361 force-pushed the disabledbg branch 2 times, most recently from 887f638 to d8bae1e Compare February 7, 2018 23:20
@mikem8361 mikem8361 force-pushed the disabledbg branch 6 times, most recently from d88ad04 to 017bb59 Compare February 26, 2018 23:28
@mikem8361
Copy link
Copy Markdown
Author

@RussKeldorph, @hseok-oh. @janvorli, @dotnet/arm32-contrib , @jkotas

I need help with armel Tizen leg that keeps fail with my changes. I don't have any idea how my changes are causing these tests to repeatable fail with my change, but master without my changes passes most of the time.

I don't have any hardware, access to any or the ramp time to repro this bug.

@alpencolt
Copy link
Copy Markdown

@sergign60 could you take a look?

@RussKeldorph
Copy link
Copy Markdown

@mikem8361 Have you tried your changes on a Raspberry Pi running Linux? That scenario is much closer to Linux/x64 and should be easier to investigate. If it doesn't repro there and only repros on Tizen, then I think we're going to have to enlist Samsung's help regardless.

@okodron
Copy link
Copy Markdown

okodron commented Mar 6, 2018

@RussKeldorph, is current CI issue related with #12972?

@RussKeldorph
Copy link
Copy Markdown

@okodron We have chalked most of the intermittent Tizen qemu CI failures up to #6298. However, I've never seen as many tests fail in a single job as are failing on this PR. I think there's a good chance @mikem8361 is right that this PR is causing or exposing another issue. We would appreciate help in investigating.

@hqueue @hseok-oh

@mikem8361
Copy link
Copy Markdown
Author

FYI @lt72

@lt72
Copy link
Copy Markdown

lt72 commented Mar 8, 2018

@hqueue @hseok-oh @okodron @sergign60: this issue is blocking one important scenario. Could any of you please see what the issue is that causes the problem?
We do not have the HW to try and repro and we would prefer not to have to do that anyway...


15:52:10 FAILED   - JIT/Directed/coverage/importer/ldelemnullarr2/ldelemnullarr2.sh
15:52:10                BEGIN EXECUTION
15:52:10                /home/coreclr/bin/tests/Windows_NT.x64.Checked/Tests/coreoverlay/corerun ldelemnullarr2.exe
15:52:10                qemu: Unsupported syscall: 389
15:52:10 
               ./ldelemnullarr2.sh: line 243:   370 Segmentation fault      (core dumped) $_DebuggerFullPath "$CORE_ROOT/corerun" $ExePath $CLRTestExecutionArguments```

@mikem8361 mikem8361 force-pushed the disabledbg branch 2 times, most recently from 8d092c1 to 3e12581 Compare March 13, 2018 01:19
@okodron
Copy link
Copy Markdown

okodron commented Mar 15, 2018

All the test from tests/testsRunningInsideARM.txt pass on the real ARM Tizen device.

sh-3.2# ./runtest.sh --sequential --testRootDir=/home/owner/managed-tests/ --coreOverlayDir=/home/owner/coreclr/ --testNativeBinDir=/home/owner/tests/ --testDirFile=/home/owner/tests/testsRunningInsideARM.txt 
Running on  CPU- arm
Skipping crossgen of FX assemblies.
Skip preparing for GC stress test. Dependent package is not supported on this architecture.
The tests have been prepared
The tests have been prepared
         - JIT/Directed/coverage/importer/ldelemnullarr2/ldelemnullarr2.sh
The tests have been prepared
         - JIT/Methodical/Coverage/b39946/b39946.sh
The tests have been prepared
         - JIT/Methodical/tailcall/_il_dbgtest_3b/_il_dbgtest_3b.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M09.5-PDC/b26863/b26863/b26863.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M09.5-PDC/b28037/b28037/b28037.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M09.5-PDC/b29068/b29068/b29068.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M09.5-PDC/b32560/b32560/b32560.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b31878/b31878/b31878.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b36332/b36332/b36332.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b37131/b37131/b37131.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b37608/b37608/b37608.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b39217/b39217/b39217.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b39946/b39946/b39946.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b41488/b41488/b41488.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b47975/b47975/b47975.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b49809/b49809/b49809.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b80045/b80045/b80045.sh
The tests have been prepared
         - JIT/Regression/CLR-x86-JIT/V2.0-Beta2/b091942/b091942/b091942.sh
The tests have been prepared
         - JIT/Regression/VS-ia64-JIT/V1.2-M01/b12263/b12263/b12263.sh
The tests have been prepared
         - JIT/Regression/VS-ia64-JIT/V1.2-M02/b26496/b26496/b26496.sh
The tests have been prepared
         - JIT/Regression/VS-ia64-JIT/V2.0-RTM/b539509/b539509/b539509.sh
The tests have been prepared
         - JIT/SIMD/VectorReturn_ro/VectorReturn_ro.sh
         - Loader/classloader/methodoverriding/regressions/549411/exploit/exploit.sh

=======================
     Test Results
=======================
# CoreCLR Bin Dir  : 
# Tests Discovered : 23
# Passed           : 23
# Failed           : 0
# Skipped          : 0
=======================
2 minutes and 26 seconds taken to run CoreCLR tests.

It looks like the problem is in the qemu itself. However I'll check the presence of that "qemu-unsupported" membarrier() syscall.

@mikem8361
Copy link
Copy Markdown
Author

@okodron please let me know when I can merge this PR. Thanks.

@okodron
Copy link
Copy Markdown

okodron commented Mar 16, 2018

I used strace on Tizen ARM device and didn't find any calls of membarrier().
However liblttng-ust library uses membarrier() syscall via liburcu library. liblttng-ust was not loaded on my Tizen ARM device. Maybe it's loaded in qemu-environment and this leads to call of "unsupported" syscall due to the usage of old qemu 2.0.
I think this issue is only specific to old qemu ARM environment. There were another PRs (#16429 #16535) with the same Tizen CI issue.
@mikem8361 can you merge this PR with tests passing on a real device but failing on qemu?

@mikem8361
Copy link
Copy Markdown
Author

What branch do you want me to merge? Master?

@mikem8361
Copy link
Copy Markdown
Author

I just merged with the latest master.

@mikem8361
Copy link
Copy Markdown
Author

I have another completely independent change in PR #16978 that is also failing the Tizen legs. I'm going merge this PR real soon now.

@okodron
Copy link
Copy Markdown

okodron commented Mar 17, 2018

@mikem8361 , thank you!
I'll have a look at #16978 too.

@mikem8361 mikem8361 merged commit 828c6c3 into dotnet:master Mar 17, 2018
@mikem8361 mikem8361 deleted the disabledbg branch March 19, 2018 18:56
@mikem8361 mikem8361 removed the * NO MERGE * The PR is not ready for merge yet (see discussion for detailed reasons) label Mar 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants