GemStone builds currently broken about smalltalkci HOT 7 CLOSED

A fix has been sent to Travis: travis-ci/travis-build#596

from smalltalkci.

Hmmm, the patch was merged 2 hours ago, but I'm still getting a syntax error ... any idea what the lag time is between the merge and it actually showing up?

from smalltalkci.

Just because it is merged doesn't mean it is in production. But it will be with the next release I guess.

However, I already noticed a different problem: moby/moby#8902
I'm afraid this could mean that we aren't able to set the hostname in container-based builds.
Can you think of a way to use the random hostname that is provided by Travis?

from smalltalkci.

well the problem is that hostname returns the "wrong answer" --- it is
not in /etc/hosts ... so I suppose the workaround would be to add the
result of hostname to the /etc/hosts... for gemstone to function the
result of hostname needs to be in /etc/hosts

--- we cannot make those kinds of changes to the older versions of the
product and it isn't likely that we'll change a future version of the
product just so that we'll work on travis ---

On 1/14/16 5:08 PM, Fabio Niephaus wrote:

Just because it is merged doesn't mean it is in production. But it
will be with the next release I guess.

However, I already noticed a different problem: moby/moby#8902
moby/moby#8902
I'm afraid this could mean that we aren't able to set the hostname in
container-based builds.
Can you think of a way to use the random hostname that is provided by
Travis?

—
Reply to this email directly or view it on GitHub
#38 (comment).

from smalltalkci.

So, adding the hostname to the /etc/hosts is still a workaround and requires a product change?
Correct?
It does work fine for OS X, because they don't run on the container-based infrastructure, but it'd still be nice to get this working somehow.

BTW: it seems that the patch still hasn't been deployed yet.

from smalltalkci.

On 1/15/16 2:06 AM, Fabio Niephaus wrote:

So, adding the hostname to the |/etc/hosts| is still a workaround and
requires a product change?
Correct?

No. If smalltalkCI.rb adds the result of hostname to /etc/hosts and
travis-ci does not blow it's lunch then there is no need for a GemStone
product change ...

Again. GemStone expects the host name answered by the /bin/hostname to
be present in /etc/hosts. If you look at an un-modified travis
container(?), the result of /bin/hostname is not present in /etc/hosts.

The original workaround was to a) add travis.dev to /etc/hosts and
then b) arrange to change the host name to travis-dev.

The next thing to try is to take the result of /bin/hostname and add
it to /etc/hosts ... if travis will let you do that then GemStone should
run fine...

It does work fine for OS X, because they don't run on the
container-based infrastructure, but it'd still be nice to get this
working somehow.

Agreed.

BTW: it seems that the patch still hasn't been deployed yet.

—
Reply to this email directly or view it on GitHub
#38 (comment).

from smalltalkci.

The patch has been deployed but it still isn't enough to get GemStone tests running. A new one is on the way...I'm closing this in favor of #28.

from smalltalkci.