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

Engine Tests crash in Mono Latest #211

Closed
rprouse opened this issue Apr 25, 2017 · 4 comments
Closed

Engine Tests crash in Mono Latest #211

rprouse opened this issue Apr 25, 2017 · 4 comments

Comments

@rprouse
Copy link
Member

rprouse commented Apr 25, 2017

See https://travis-ci.org/nunit/nunit-console/jobs/217230850

Not sure if we made the Travis Linux/Mono/Latest build no longer required because of this or another failure, but I am also getting this on my local box with Mono 4.8.1 so it isn't a Travis issue.

Most of the error is probably useless to us, but it begins with,

* Assertion: should not be reached at sgen-scan-object.h:90

and ends with

=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

Not sure what we are going to do about it.

@rprouse
Copy link
Member Author

rprouse commented Apr 25, 2017

Just did a little searching through the history. This has been happening since #45 where mono:latest was added. It was failing with a similar issue then with Mono 4.2.4.

@tom-dudley
Copy link
Contributor

#44 looks to be the same issue.

@ChrisMaddock
Copy link
Member

This seems to be fixed with the current mono latest, 5.0.1.1.
https://travis-ci.org/nunit/nunit-console/builds/236200004?utm_source=github_status&utm_medium=notification

mono bug? I'll close, please reopen if people think we should look into it further.

@rprouse
Copy link
Member Author

rprouse commented May 26, 2017

I think it is a mono bug. The nunit framework tests started doing the same thing with Mono 5.0. I wonder if it is fixed in 5.0.1.1 too?

@rprouse rprouse modified the milestone: Closed Without Action May 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants