GNOME Bugzilla – Bug 653195
banshee-community-extensions-2.0.0: test fails
Last modified: 2011-09-26 12:38:26 UTC
As reported downstream at: http://bugs.gentoo.org/show_bug.cgi?id=372615 Test fails with the following error: Making check in build Making check in m4 Making check in help xmllint --noout --noent --path C:./C --xinclude --relaxng /usr/share/xml/mallard/1.0/mallard.rng ./C/AlarmClock.page ./C/AlarmClock.page validates xmllint --noout --noent --path C:./C --xinclude --relaxng /usr/share/xml/mallard/1.0/mallard.rng ./C/AlarmClock-alarm.page ./C/AlarmClock-alarm.page validates xmllint --noout --noent --path C:./C --xinclude --relaxng /usr/share/xml/mallard/1.0/mallard.rng ./C/AlarmClock-sleep.page ./C/AlarmClock-sleep.page validates Making check in src Making check in AlarmClock Making check in Ampache Making check in AppIndicator Making check in Awn Making check in ClutterFlow Making check in ClutterFlow Making check in Banshee.ClutterFlow Making check in CoverWallpaper Making check in Jamendo Making check in LastfmFingerprint Making check in liblastfmfpbridge Making check in Banshee.LastfmFingerprint Making check in LCD Making check in Lirc Making check in lirc-glue Making check in Banshee.Lirc Making check in NUnitTests Making check in GUITestHarness Making check in LiveRadio Making check in Lyrics Making check in Magnatune Making check in Mirage Making check in libmirageaudio Making check in Mirage Making check in Banshee.Mirage Unhandled Exception: System.Security.SecurityException: No access to the given key at Microsoft.Win32.KeyHandler..ctor (Microsoft.Win32.RegistryKey rkey, System.String basedir, Boolean is_volatile) [0x00057] in /mnt/gen2/tmpdir/portage/dev-lang/mono-2.10.2/work/mono-2.10.2/mcs/class/corlib/Microsoft.Win32/UnixRegistryApi.cs:138 at Microsoft.Win32.KeyHandler..ctor (Microsoft.Win32.RegistryKey rkey, System.String basedir) [0x00000] in <filename unknown>:0 at Microsoft.Win32.KeyHandler.Lookup (Microsoft.Win32.RegistryKey rkey, Boolean createNonExisting) [0x00096] in /mnt/gen2/tmpdir/portage/dev-lang/mono-2.10.2/work/mono-2.10.2/mcs/class/corlib/Microsoft.Win32/UnixRegistryApi.cs:401 at Microsoft.Win32.UnixRegistryApi.OpenSubKey (Microsoft.Win32.RegistryKey rkey, System.String keyname, Boolean writable) [0x00000] in /mnt/gen2/tmpdir/portage/dev-lang/mono-2.10.2/work/mono-2.10.2/mcs/class/corlib/Microsoft.Win32/UnixRegistryApi.cs:842 at Microsoft.Win32.RegistryKey.OpenSubKey (System.String name, Boolean writable) [0x0001e] in /mnt/gen2/tmpdir/portage/dev-lang/mono-2.10.2/work/mono-2.10.2/mcs/class/corlib/Microsoft.Win32/RegistryKey.cs:278 at Microsoft.Win32.RegistryKey.OpenSubKey (System.String name) [0x00000] in /mnt/gen2/tmpdir/portage/dev-lang/mono-2.10.2/work/mono-2.10.2/mcs/class/corlib/Microsoft.Win32/RegistryKey.cs:262 at (wrapper remoting-invoke-with-check) Microsoft.Win32.RegistryKey:OpenSubKey (string) at NUnit.Util.SettingsService.ConvertLegacySettings () [0x00000] in /mnt/gen2/tmpdir/portage/dev-lang/mono-2.10.2/work/mono-2.10.2/mcs/nunit24/ClientUtilities/util/Services/SettingsService.cs:53 at NUnit.Util.SettingsService..ctor () [0x00053] in /mnt/gen2/tmpdir/portage/dev-lang/mono-2.10.2/work/mono-2.10.2/mcs/nunit24/ClientUtilities/util/Services/SettingsService.cs:35 at NUnit.ConsoleRunner.Runner.Main (System.String[] args) [0x000c6] in /mnt/gen2/tmpdir/portage/dev-lang/mono-2.10.2/work/mono-2.10.2/mcs/nunit24/ConsoleRunner/nunit-console/Runner.cs:47 at NUnit.ConsoleRunner.Class1.Main (System.String[] args) [0x00000] in /mnt/gen2/tmpdir/portage/dev-lang/mono-2.10.2/work/mono-2.10.2/mcs/nunit24/ConsoleRunner/nunit-console-exe/Class1.cs:22 make[3]: *** [test] Error 1 make[2]: *** [check-recursive] Error 1 make[1]: *** [check-recursive] Error 1 make: *** [check-recursive] Error 1 Thanks for fixing this
Still the same with 2.0.1 :(
I was not able to reproduce this problem (Ubuntu 11.04). Are you sure nunit is set up properly ? It seems it's trying to access the Windows Registry, which is weird... Could you try running the unit test manually ? You can look into build/build.rules.mk to see how it is run.
Looks like it only fails when building under portage (under sandbox and not as my user), maybe some environment variable needs to be redefined or unset :-/ About build.rules.mk, this is its content related with this: test: $(ASSEMBLY_FILE) if test "x$(TEST_ASSEMBLY)" = "xyes"; then \ LD_LIBRARY_PATH="$(BANSHEE_LIBDIR):$(BANSHEE_EXTDIR):$(EXTENSION_DIR)/..:$(EXTENSION_DIR)${LD_LIBRARY_PATH+:$LD_LIBRARY_PATH}" \ MONO_PATH="$(BANSHEE_LIBDIR):$(BANSHEE_EXTDIR):$(EXTENSION_DIR)/..:$(EXTENSION_DIR)${MONO_PATH+:$MONO_PATH}" \ $(NUNIT_CONSOLE) -nologo -noshadow $(ASSEMBLY_FILE); \ fi nunit is supplied by mono-2.10.4
This is still the same with 2.2.0 and mono-2.10.5 :(
I had a quick look at the nunit code included in mono : https://github.com/mono/mono/blob/master/mcs/nunit24/ClientUtilities/util/Services/SettingsService.cs#L24 It looks like nunit only tries to access the registry when it can't find its configuration file. So my guess is that the same problem would happen for anything using nunit-console in the portage sandbox. In that case, the problem would be with the nunit code in mono. Are there any other packages with nunit tests that work in the portage sandbox ?
Looks like google-gdata-sharp tests also failed in a similar way: https://bugs.gentoo.org/show_bug.cgi?id=310101 I don't know about other packages failing in similar ways :/
That seems to confirm my idea that the problem is in nunit itself, or portage. You could file a bug against mono, as they are shipping nunit in their source: http://bugzilla.xamarin.com/ Or against nunit itself (Don't know where their bug tracker is). I'm closing this as NOTGNOME, as the problem is not with Banshee or the Community Extensions. Feel free to re-open it if there's something we can do on our side.
Done, thanks for helping me with this :D