Oolite Bulletins

Zireael wrote:

Cim pushed the fixes for tutorial yesterday. I was hoping today's nightly would have them in, but it seems terrastorage hasn't updated.

This is why I have a druid's name. Because I know when the newly brewed magic potion will blow to my face.
I am on it to fix the issue. I will post an estimated time of availability as soon as I find the root-cause.

In the meantime, and as much as this can worth, the rsync update (as described above) is functional for both 32bit and 64bit oolite nightly builds.

Sorry guys and gals, the lack of a test-server is obvious here.

32bit Oolite nightly build web page is available.
Root cause analysis for today's failure is still in progress.

64bit Oolite nightly build web page is available too.
Root cause analysis for today's failure is still in progress.

Some minor fixes have been performed to the nightly web pages scripts.
However, it doesn't seem to me that what is addressed by these fixes,
caused today's unavailability.

I need to take care of my WAF (i.e. wife acceptance factor ) now, therefore,
I will wait till the next nightly release occurs to see if the case is solved.

This is just to close this case. The issue was generated by a script executed too early.
Following too nightly updates it is considered fixed.

The rsync seems to work like a charm reducing dramatically the data downloaded per nightly.

Cheers!

Getafix wrote:

The rsync seems to work like a charm reducing dramatically the data downloaded per nightly.

Indeed! I had to tinker with the command line a little, but it seems to work - as you say - like a charm! Thanks again, amigo.

Cody wrote:

...I had to tinker with the command line a little...

Hint: There is a cwrsync.cmd in the root installation folder of cwrsync.
Edit this and add the following line at the end of the file:

Oolite nightly 64bit Oolite nightly 32bit If Windows is 32bit (and you have kept the original cwrsync installation) then you need to change the rsync path removing
the " (x86)" form the path. There is a space before the left parenthesis that needs to be removed too.
This line of code also assumes default installation path for Oolite nightly too... change it as per your needs... keeping the /cygdrive/ of course.

Create a shortcut of cwrsync.cmd wherever is handy for you and you are now one double-click away from rsync-ing getting the latest nightly!
(Cudos to AC for pointing this out!)

For those with the Cygwin environment on their systems a cron job can bet set up to do this in the background. You would need to install the Cygwin version of rsync and cron.

Showing my ignorance here perhaps, but if I add: to cwrsync.cmd, it won't let me save it (using Notepad++). Instead, it asks me to check if this file is open in another program.
I'm obviously doing something wrong - so I'll use the manual method again.

@Cody
Execute notepad++ as administrator by right-clicking on notepad++ executable/icon.

Then open cwrsync.cmd.

<face/palm> Nurse, nurse... is it time for my medication?

Cody wrote:

<face/palm> Nurse, nurse... is it time for my medication?

What I really enjoy in this community is the great sense of humor.
Visualizing your expression (and the face/palm) while reading the answer, gave me a good laugh man!
If only I could take advantage of the chance to meet you guys and gals! <sigh>

The nightly server will have service unavailability periods
as of 26/Mar 16:00 UTC till 26/Mar 23:00 UTC
due to maintenance activities.


EDIT 2014/03/26 23:25 UTC: Maintenance activities completed.


As a result of these activities the nightly service might not deliver
the latest build the 27th of March.

It is expected that as of 28/Mar 07:00am UTC the nightly service will be stabilized.

Mac users may alternatively use the following URL:
http://oolite.org/nightly/mac/index.php


EDIT 2014/03/27 08:05 UTC:
Nightly build service has been fully restored.
Thank you for your patience.

Getafix wrote:

Nightly build service has been fully restored. Thank you for your patience.

<chortles> Thank you, sir!

Cody wrote:

Getafix wrote:

Nightly build service has been fully restored. Thank you for your patience.

<chortles> Thank you, sir!

The first thing that blew to my face was the Windows nightly.
To be honest with the community, Windows VM didn't like at all the CPU degrade (yes... DEgrade ) that I tried to experiment with!
Then, the Linux 64bit VM had the same opinion as the Windows VM.

Anticipating the crowd's reaction (see here, especially the part 1:27-2:00), I restored it back.

So now, I will have to buy a used Core 2 Duo Quad, for my aged motherboard, to be prepared for E/D Beta release.
(...off topic alert...off topic alert...off topic alert...)