bouncing source.squeak.org

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

bouncing source.squeak.org

Chris Muller-3
I just looked at the image and there were bunch of processes hung up on one or another of two critical blocks; although it did not appear that either was part of the call stack of the other.

One of them was using a Semaphore instead of a Mutex, so that is suspicious.

There were so many, it wasn't evident what the root cause of the issue was, so I decided to bounce the server and will monitor it over the next days to see if the issue returns.



On Fri, Dec 30, 2016 at 2:34 AM, Fabio Niephaus <[hidden email]> wrote:
On Fri, Dec 30, 2016 at 12:18 AM Chris Muller <[hidden email]> wrote:
Appears there is a problem accessing one of the MCVersions -- #versionNamed: returned nil, but the calling code didn't expect that.

Very helpful would be to know what version it failed on..


Yes, that'd be helpful. But I'm afraid we only have a call stack at the moment. Interestingly, the error only seems to occur occasionally, so maybe we need one more retry somewhere in the updater? Obviously, the updater needs to be as bullet proof as possible, because it's used to build new trunk images.
 

On Tue, Dec 27, 2016 at 12:35 PM, Fabio Niephaus <[hidden email]> wrote:
Trunk builds are failing because of:

UndefinedObject(Object)>>doesNotUnderstand: #dependencies MCMcmUpdater>>updateFromConfig: [] in [] in [] in MCMcmUpdater>>updateFromRepository:
...


--

On Tue, Dec 27, 2016 at 4:45 PM Travis CI <[hidden email]> wrote:
squeak-smalltalk / squeak-app (master)
Build #320 was broken.
14 minutes and 20 seconds
Fabio Niephaus 87356bd Changeset →
  Exclude SqueakSSLTest

Want to know about upcoming build environment updates?

Would you like to stay up-to-date with the upcoming Travis CI build environment updates? We set up a mailing list for you! Sign up here.

Documentation about Travis CI
Need help? Mail [hidden email]!
Choose who receives these build notification emails in your configuration file.

Would you like to test your private code?

Travis CI for Private Projects could be your new best friend!












Reply | Threaded
Open this post in threaded view
|

Re: bouncing source.squeak.org

Nicolas Cellier


2016-12-31 0:15 GMT+01:00 Chris Muller <[hidden email]>:
I just looked at the image and there were bunch of processes hung up on one or another of two critical blocks; although it did not appear that either was part of the call stack of the other.

One of them was using a Semaphore instead of a Mutex, so that is suspicious.

There were so many, it wasn't evident what the root cause of the issue was, so I decided to bounce the server and will monitor it over the next days to see if the issue returns.



Could it be related to the timeout we experiment each time we commit a package?
 

On Fri, Dec 30, 2016 at 2:34 AM, Fabio Niephaus <[hidden email]> wrote:
On Fri, Dec 30, 2016 at 12:18 AM Chris Muller <[hidden email]> wrote:
Appears there is a problem accessing one of the MCVersions -- #versionNamed: returned nil, but the calling code didn't expect that.

Very helpful would be to know what version it failed on..


Yes, that'd be helpful. But I'm afraid we only have a call stack at the moment. Interestingly, the error only seems to occur occasionally, so maybe we need one more retry somewhere in the updater? Obviously, the updater needs to be as bullet proof as possible, because it's used to build new trunk images.
 

On Tue, Dec 27, 2016 at 12:35 PM, Fabio Niephaus <[hidden email]> wrote:
Trunk builds are failing because of:

UndefinedObject(Object)>>doesNotUnderstand: #dependencies MCMcmUpdater>>updateFromConfig: [] in [] in [] in MCMcmUpdater>>updateFromRepository:
...


--

On Tue, Dec 27, 2016 at 4:45 PM Travis CI <[hidden email]> wrote:
squeak-smalltalk / squeak-app (master)
Build #320 was broken.
14 minutes and 20 seconds
Fabio Niephaus 87356bd Changeset →
  Exclude SqueakSSLTest

Want to know about upcoming build environment updates?

Would you like to stay up-to-date with the upcoming Travis CI build environment updates? We set up a mailing list for you! Sign up here.

Documentation about Travis CI
Need help? Mail [hidden email]!
Choose who receives these build notification emails in your configuration file.

Would you like to test your private code?

Travis CI for Private Projects could be your new best friend!
















Reply | Threaded
Open this post in threaded view
|

Re: bouncing source.squeak.org

Chris Muller-4

Could it be related to the timeout we experiment each time we commit a package?

It could be.  I never experienced the timeout myself, so wondered whether it was doing a GC at that moment.  It could have been this..