87905 - debug menu entries are mostly broken

Status: RESOLVED FIXED

(SeaMonkey :: Build Config, defect, P3)

Description

[Jeremy M. Dolan]

...and have been for months. They simply do not load.

Examples include:

Verification->Transparency
Verification->JPEG
Viewer Demos->(all of them)
XPToolkit->(all of them)

Comment 1

[Asa Dotzler [:asa]]

possibly a packaging issue.  We have all these working on win32.  

Comment 2

[Jon Granrose]

what build?  your own debug build or one of the installer builds?  I suspect
this is that the installer builds still have the debug menu but the underlying
files are not there and that this bug should be to remove the debug menu in the
installer builds.

Comment 3

[Jeremy M. Dolan]

Every linux installer verif build (and I think normal linux .tar.gz verif
builds) for the past 4-6 months. I figured this was known and didn't bother to
report it until now, when no one on #mozilla thought it was broken.

Comment 4

[Jeremy M. Dolan]

> that this bug should be to remove the debug menu in the installer builds.

I'd like to see non-milestone nightly verification builds still include the
Debug and QA menus, regardles of weither it's installed with the installer or
not. I use the installer to test it, and to save mozilla.org and myself
bandwidth by unchecking mail/news and chatzilla, which I have no interest in
using/testing. The purpose of the nightlies are testing, it wouldn't make much
sense to remove the debug and qa menus from them, regardless of how the files
are downloaded.

Comment 5

[Akkana Peck]

I noticed that some of the items I used in the editor's debug menu (e.g.
Output*) stopped working a month or so ago.  That's true even in my debug build.

I'm not sure if this is a general problem or not.  Are other debug menus working
in debug builds, and broken only in release builds?  I need to know whether to
file a separate bug on the editor menus or not.

Comment 6

[Jeremy M. Dolan]

heh... this is targeted for 1.0, but the debug menu will be removed for 1.0, I'd
assume. Preferably someone could take a look at this before, so QA people can
actually make use of the menu while there's still time?

Comment 7

[cls]

*** Bug 99329 has been marked as a duplicate of this bug. ***

Comment 8

[cls]

So the problem is that in most (all?) cases the res/ files are installed from
what turns out to be a 'test' directory.  Since the releases are made with
--disable-tests, viewer isn't even built...much less its demos.

Removing the --disable-tests means that the release tarballs (nightlies
included) will contain the extra "junk" that we build by default.  The installer
builds should contain only the extra res/* files since we specify them in the
package file.

Building certain tests by regardless of the --disable-tests setting will cause
bogus bugreports.  See the TestGtkEmbed bugs as evidence of that.

Playing with makefile ordering to grab just the resource files....

Comment 9

[cls]

Attachment: Export viewer samples from toplevel webshell makefile

Comment 10

[jag (Peter Annema)]

Comment on attachment 50212 [details] [diff] [review]
Export viewer samples from toplevel webshell makefile

r=jag

Comment 11

[cls]

Patch checked in.

Comment 12

[hacker formerly known as [e-mail]]

*** Bug 29565 has been marked as a duplicate of this bug. ***