joaquimcid / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

Icarus not showing up #576

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Just installed the 3.1.367 on a 64bit Windows 7. I've got the test runner
factory set to TypeMock.

When I try to launch Icarus, it doesn't show up, no error messages nothing.
The assembly binding log says it can't find Gallio.TypeMockIntegration.
It's looking in for file:///E:/Program Files
(x86)/Gallio/bin/Gallio.TypeMockIntegration.DLL and other similar
locations, but never in the plugin folder. 

Copying the Typemock-related files to the bin folder solves the issue.

Original issue reported on code.google.com by uluhonol...@gmail.com on 29 Oct 2009 at 4:49

GoogleCodeExporter commented 8 years ago
Bizarre.

Original comment by jeff.br...@gmail.com on 29 Oct 2009 at 5:18

GoogleCodeExporter commented 8 years ago
I've had problem with Icarus not showing up a few times,
and after some random trial and error I discovered that
removing the Gallio.Icarus.exe.config file helps.
Never found out why though

Original comment by niklas.d...@gmail.com on 8 Nov 2009 at 9:53

GoogleCodeExporter commented 8 years ago
Might change which version of the .Net runtime gets used.  With the .config 
file,
it'll use v4.0 if installed.

Original comment by jeff.br...@gmail.com on 8 Nov 2009 at 10:02

GoogleCodeExporter commented 8 years ago
That might be it, I had 4.0 Beta 1 installed at that time

Original comment by niklas.d...@gmail.com on 8 Nov 2009 at 10:21

GoogleCodeExporter commented 8 years ago
Me, I don't have the 4.0. The problem was related to the testrunner factory 
setting.
When I changed it manually in the config file (found in the AppData directory) 
to
another setting, Icarus began to show up.

Original comment by uluhonol...@gmail.com on 8 Nov 2009 at 11:03

GoogleCodeExporter commented 8 years ago
I am trying to run Gallio 3.1 Icarus on Windows Server 2003 x64. I try starting
Icarus and it never comes up. I haven't found any errors no matter where I 
look. I've
attempted to follow the suggestions above... removing the config file just 
causes
Icarus to crash with the "Icarus has encountered a problem and needs to close."
dialog. I've tried commenting out the .Net runtime entry for 4.0, but Icarus 
just
doesn't start. I also tried to change the testrunning setting, using the Gallio
control panel, but that seemed to have no impact on the "no startup" behavior.

(please note that I am trying 3.1 because with 3.0.6 Icarus starts but displays 
no
tests on my x64 system. I figure using the latest version is preferable, but I 
need
it to work to be able to do that).

Original comment by marc.gib...@gmail.com on 9 Nov 2009 at 10:33

GoogleCodeExporter commented 8 years ago
Two things:

1. I have fixed several x64 issues in recent builds.  Try the latest v3.1 from
http://ccnet.gallio.org/Distributables/ unless you're already running something
reasonably recent.

2. Please try forcing Icarus to 32bit mode to see if that changes things.  I 
suspect
you're seeing the AccessViolationException that others have reported (but that I
cannot reproduce).

To do so, use corflags.exe.  You'll find it in the Windows SDK and .Net 
Framework SDK
tools.

corflags.exe /32bit+ Gallio.Icarus.exe

Original comment by jeff.br...@gmail.com on 10 Nov 2009 at 7:21

GoogleCodeExporter commented 8 years ago
This is weird, but.. I reinstalled TypeMock recently, don't know if it has had 
any
impact, but Icarus started to show up even with the TypeMock runner factory 
selected.
So, in my case, the issue has been auto-resolved.

@marc.gibian: I had to change the runner factory setting manually in the config 
file
found in the AppData\Gallio\Icarus folder.

Original comment by uluhonol...@gmail.com on 10 Nov 2009 at 1:26

GoogleCodeExporter commented 8 years ago
On a second thought, I remember I also disabled startup loading of the last 
project.
That might have fixed it.

Original comment by uluhonol...@gmail.com on 10 Nov 2009 at 1:59

GoogleCodeExporter commented 8 years ago
Found the Icarus.settings file ... changing testRunnerFactory from the existing 
value
of "NCover" did not have any impact. But, I noticed the recentProjects section, 
so I
deleted those and Icarus came right up. I'm guessing the problem is that the 
recent
projects include .gallio files from an older version (3.0.6) and that causes 
Icarus
to crash rather than fail gracefully when trying to load the most recent of the
recent projects.

Now that Icarus is up, I opened my test assemblies only to get back to the 
problem of
having no tests show up. I had this problem with 3.0.6 as well and thought 3.1 
would
fix this. Any suggestions? Can you point me at a more appropriate item/thread?

I'm pretty sure this is still an x64 issue.

Original comment by marc.gib...@gmail.com on 10 Nov 2009 at 4:38

GoogleCodeExporter commented 8 years ago
We're having a discusson about this issue on the Gallio Dev mailing list.  Kent
Hansen has figured out that the reason the problem appears to go away on its 
own is
that after a few crashes Windows sets a compatibility flag that modifies heap 
behavior.

Explained here (also show key to disable feature completely):
http://msdn.microsoft.com/en-us/library/dd744764%28VS.85%29.aspx

Original comment by jeff.br...@gmail.com on 10 Nov 2009 at 6:46

GoogleCodeExporter commented 8 years ago
Fixed thanks to some excellent sleuthing by Kent Hansen.

Original comment by jeff.br...@gmail.com on 11 Nov 2009 at 8:43