Closed Bug 195435 Opened 21 years ago Closed 21 years ago

nightly OSX build invalid - automation needs work

Categories

(SeaMonkey :: Build Config, defect)

Other Branch
PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED FIXED
mozilla1.3final

People

(Reporter: bugmail, Assigned: jj.enser)

References

()

Details

Attachments

(1 file)

There is no latest-1.3 build for Mac available from ftp.mozilla.org. In fact, it
doesn't appear there have been any 1.3 branch builds for Mac.
we know.
Assignee: seawood → jj
Target Milestone: --- → mozilla1.3final
Flags: blocking1.3?
There's one there now, but it crashes on startup.
FWIW: The crash on launch in latest-1.3 is apparently just a freaky coincidence,
unrelated to the quit on launch in latest-trunk, which is covered by bug 195654.
Keywords: crash
Summary: No latest-1.3 build for Mac → No latest-1.3 build for Mac, crash on startup, can't open libdl.0.dylib
Version: Trunk → Other Branch
The good news: latest-1.3 20030304 is a svelte 41531 byte download (1000-to-1
compression!), and doesn't crash with "can't open libdl.0.dylib".

The bad news: even after bug 195897 gets fixed, this bug might continue.
Depends on: 195897
Summary: No latest-1.3 build for Mac, crash on startup, can't open libdl.0.dylib → No latest-1.3 build for Mac, crash on startup or dmg can't mount
still crashing on attempt to start with mac mozilla build 2003-03-05-10-1.3
Odd, i fired up the build from the build machine itself and it launches fine there.
Continuing investigations...
Status: NEW → ASSIGNED
Since Talkback doesn't catch this crash, here's a log for the official record.
Summary: No latest-1.3 build for Mac, crash on startup or dmg can't mount → No latest-1.3 build for Mac, crash on startup [@ halt] or dmg can't mount
The crash on startup is a different issue discussed in bug 196115.
Let's not mix all the OSX issues please, unless we decide to make this bug a
"tracking" bug.

This was originally entered as a blocker since the bits available on the wire
were unusable (anywhere between 4Kb and 50Kb).

The proper fix for this is to improve the nightly build automation by handling
errors and not package & distribute invalid bits.

That's what this bug is all about, so I'll rename it for better clarity.
If new crashers occur, please log new bugs.
Severity: blocker → critical
Keywords: crash
Summary: No latest-1.3 build for Mac, crash on startup [@ halt] or dmg can't mount → nightly OSX build invalid - automation needs work
Sorry. Being faced with FOUR simultaneous but independent build failure bugs in
OS X was rather confusing.

But something must be working right; I'm posting this using latest-1.3 20030306.
> Being faced with FOUR simultaneous but independent build failure bugs in
> OS X was rather confusing.

Tell me about it, they're almost all mine! :-)

> But something must be working right; I'm posting this using latest-1.3
> 20030306.

That's great news. success was achieve by using a trick on the build machine
(see bug 196115)
Asa will probably cook this build when he gets to his mac. Let him know if you
find anything bad yourself. I'll see if I can get someone to smoketest it.
Flags: blocking1.3? → blocking1.3-
fixed on the trunk. (patch unavailable here because it's also doing Netscape
packaging)
for 1.3, unless something really bad breaks the build, we shouldn't see anymore
invalid bits on the wire. If it happens, they will be promptly removed.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
verified
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: