What is going on with 2.18a1 builds?

Sylph · Post by **Sylph** » February 18th, 2013, 11:02 am

It seems that since 14 February no new nightlies have been released — does anybody know what is going on?

Post by **rsx11m** » February 18th, 2013, 8:24 pm

That's Windows, Linux nightlies were last successful February 16, Mac OSX February 15.

A couple of bustages were recently introduced by the Firefox/Core developers causing everything go red over the weekend, this was resolved in the morning. Windows is still broken due to some pymake issue.

Since tomorrow is the regularly scheduled merge for the next cycle (i.e., 2.18a1 becomes 2.18a2 on the aurora channel), these problems at least initially may spill over into the aurora nightly builds as well.

Post by **rsx11m** » February 19th, 2013, 6:41 am

Nightlies proceeded for Linux and Mac OSX today, but failed again for Windows.

Post by **rsx11m** » February 19th, 2013, 7:19 am

Bugs to watch for the Windows trunk builds:

Bug 842341, Windows builds using make fail.
Bug 842445, Enable SeaMonkey win builders to build using pymake instead of make.

Post by **rsx11m** » February 20th, 2013, 7:09 am

Not unexpectedly, SeaMonkey-Aurora is now broken for Windows as well... :-(

Pim · Post by **Pim** » February 20th, 2013, 10:07 am

My nightly just updated to 2.19a1 (Build ID: 20120220003044).

Post by **rsx11m** » February 20th, 2013, 10:30 am

Linux is fine, only Windows is affected by the current issues.

therube · Post by **therube** » February 20th, 2013, 4:59 pm

Looks like this one too, Bug 842918 - SeaMonkey Windows builds are broken due to regression in disable-webRTC.

therube · Post by **therube** » March 3rd, 2013, 7:38 am

Windows builds are (finally) up :-)

.

Post by **rsx11m** » March 11th, 2013, 6:04 am

Currently no 2.19a1 nightly builds due to fallout from bug 847195. Mitigating fix in progress, approved, and awaiting to be pushed in bug 849612.

Post by **rsx11m** » March 19th, 2013, 5:45 am

Trunk builds are currently broken badly (for mail/news at least), fix in progress and hopefully landing soon. From TB Builds:

JoeS wrote:I guess this is the bug to watch for a trunk fix:
#851924 [Core:DOM: Core & HTML]-window.frames["foobar"] doesn't work in non-HTML documents [All]

If you try to run a tinderbox build, you come up with a blank 3pane.

rsx11m wrote:Phil's bug report has been marked as a duplicate. The new one to watch is #823227, Make the Global Scope Polluter work for non-html scopes.

Post by **rsx11m** » March 20th, 2013, 5:59 am

The 2.19a1 nightly builds succeeded for Windows (first trunk nightly since March 6!) and Linux, but failed for Mac OSX.

Post by **rsx11m** » March 21st, 2013, 5:22 pm

Today's Mac OSX nightly builds were successful as well, thus back on track (at least as far as the en-US trunk builds are concerned).

What is going on with 2.18a1 builds?

What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?

Re: What is going on with 2.18a1 builds?