| Summary: | nautilus-2.8.0 tests fail | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jocelyn Mayer <l_indien> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info output | ||
|
Description
Jocelyn Mayer
2004-10-09 09:11:53 UTC
can you be more verbose ? what test & how does it fail ? Whats your emerge info ? Why do I have to ask these obvious questions, you are making a bugreport right ? We are not psychic here... I already gave you the test that failed:
libnautilus-private/nautilus-file.c:6173
I wonder how could I be more precise....
The test is:
file_1 = nautilus_file_get (EEL_TRASH_URI);
EEL_CHECK_STRING_RESULT (nautilus_file_get_display_name (file_1), _("Trash"));
And eel-2.8.0 defines EEL_TRASH_URI this way:
#define EEL_TRASH_URI "trash:"
(/usr/include/eel-2/eel/eel-vfs-extensions.h:37)
So, the test fail because of case issue.
Whatever the configuration is, this test would fail, that's why I didn't post it.
It failed on 3 machines (amd46 & x86) with 3 different configurations.
However, you'll find the configuration I use on the amd64 as an attachement, if it can make you happy.
Here are the flags used for the package build:
gnome-base/nautilus-2.8.0 +cups -debug +flac +gstreamer +mad +oggvorbis
Created attachment 41461 [details]
emerge --info output
Well it's only a silly test they probably forgot to fix. Just don't try to build everything with maketest (silly features). As the machines I maintain are not toys but are used for production, and as I already had severe problems with some packages, I really want to merge with the maketest feature. This helps me know that some packages are broken before I'm blocked in my work... In this particular case, I already did decide that this test wasn't important for me and remerged this package with -maketest. But, as I had a problem, I reported it, that's all. Then, if you decide to remove this test, that's all right for me... no as said (but without looking at the code), i bet they just forgot to fix up the tests, because i doubt they run them very often themselves. I won't remove tests, i just don't take them very seriously in most packages, because they are often just not well maintained. It may be related to the other bug, altough i can't reproduce that one either. OK, will you report the bug to nautilus developpers, or should I ? Or maybe it's an eel issue: I don't know if this name change would break anything else... What's the other bug you are talking about ? wait with reporting until we had a proper look forgot to post the link : http://bugs.gentoo.org/show_bug.cgi?id=65378 |
