Skip to content
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

Tizen armrel crossbuild failure #8676

Closed
joshfree opened this issue Aug 2, 2017 · 3 comments
Closed

Tizen armrel crossbuild failure #8676

joshfree opened this issue Aug 2, 2017 · 3 comments

Comments

@joshfree
Copy link
Member

joshfree commented Aug 2, 2017

https://ci.dot.net/job/dotnet_coreclr/job/release_uwp6.0/job/armel_cross_release_tizen_prtest/36/

02:00:55 The tests have been prepared
02:00:56          - JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b31878/b31878/b31878.sh
02:00:57 The tests have been prepared
02:01:02 FAILED   - JIT/Regression/CLR-x86-JIT/V1-M11-Beta1/b36332/b36332/b36332.sh
02:01:02                BEGIN EXECUTION
02:01:02                /home/coreclr/bin/tests/Windows_NT.x64.Release/Tests/coreoverlay/corerun b36332.exe
02:01:02 
               qemu: uncaught target signal 11 (Segmentation fault) - core dumped
02:01:02                ./b36332.sh: line 243:   505 Segmentation fault      (core dumped) $_DebuggerFullPath "$CORE_ROOT/corerun" $ExePath $CLRTestExecutionArguments
02:01:02                Expected: 100
02:01:02                Actual: 139
02:01:02                END EXECUTION - FAILED
02:01:04 The tests have been prepared
@BruceForstall
Copy link
Member

@dotnet/arm32-contrib

@jyoungyun
Copy link
Contributor

These assertion occurs intermittently because our test ci runs on qemu instead of real target. It is related to qemu so it will continue to occur unless we use a real target. We plan to modify the code to retry if the test ci fails.

@RussKeldorph
Copy link
Contributor

RussKeldorph commented Nov 2, 2017

Dup of #6334

@msftgits msftgits transferred this issue from dotnet/coreclr Jan 31, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Dec 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants