Oolite Mac OS X – Trunk nightly builds

[JensAyton]

Getafix is working on a nicer nightly page, but in the mean time,Mac nighties are available here:
GitHub Oolite Nightly Releases repository.

The nightly is the latest version of trunk Oolite and Debug.oxp at the time the script runs (04:30 CE(S)T, for my convenience), assuming it builds without errors.


Edit by a_c, 25 May 2017: Updated with new location for the nightlies,

[Ramirez]

Thanks Ahruman, that's great. Now I've got no excuse not to get on and finish some of the projects I started ages ago.

[Getafix]

A slightly updated Mac OS X nightly build status page,
similar to the one published for Windows and Linux, can be found here.

The installation zip-file setup is still hosted in Ahruman's server.

[Pluisje]

The nightly build 3165 is missing the MacOS map. This results in the message "not supported by this architecture" (or something like that, this is a translation).

[another_commander]

The nightly build 3165 is missing the MacOS map. This results in the message "not supported by this architecture" (or something like that, this is a translation).

A glitch in the system, I'm afraid. If you look at the nightly page details, all builds are reported as failed, yet the Mac managed to somehow generate a distribution zip. You will have to wait tomorrow's nightly for a fix, I guess.

[JensAyton]

Last night’s build ran and gave a notification that it had successfully uploaded, but actually wasn’t. Not sure what happened there. You’re not missing anything very exciting, anyway.

[Getafix]

Since Windows is also synchronized to Mac nightlies, no nightly for Windows too.

Getafix is thinking: Hmm... I should probably break the revision synchronization between the three OS nightlies.

Linux nightly is intentionally paused today. Read here.

[JensAyton]

Starting tonight, the Mac nightly will perform extra checks for JavaScript memory management errors. These errors will provide actually useful information in the log file (immediately before crashing), and it’s extra important that they’re reported.

[Corny]

I'm looking forward to test that since my old trunk crashed every time I jumped to a specific system, supposedly because some weird JS in an OXP.

[Kaks]

Looking forward to getting your bug reports!
Plus, and that goes for everyone, really, if you see a crash to desktop please let us know as soon as you can, including ways of repeating that crash, & any other relevant info you might have.

It definitely helps us to get a better Oolite!

[Corny]

I sent it to Cmdr. James who suggested trying the next nightly since he believed the crash was caused by an error that was fixed after r3471.
If it persists, I'll certainly post all my reports if I don't find the OXP that causes the crash.

[another_commander]

If it persists, I'll certainly post all my reports if I don't find the OXP that causes the crash.

If it persists, please post all of your reports regardless.

[JensAyton]

“An OXP did it” is not a reason to disregard a bug. In fact, it makes it worse.

[Cmdr James]

There are two objectives here, to establish precisely the cause of the failure in an OXP and also in oolite. It is likely that both should be fixed, although I guess it is possible that the OXP is doing something legal and still killing oolite.

My sugestion to try again today was based around fixes that the dev team made yesterday, and my inability to reproduce the failure on my trunk build.

[Eric Walch]

I'm looking forward to test that since my old trunk crashed every time I jumped to a specific system, supposedly because some weird JS in an OXP.

Which system? Its not by accident a communistic system of tech level > 9 ?