search

GsDevKit / GsDevKit_home

master GsDevKit project
http://gsdevkit.github.io/GsDevKit_home
MIT License
31 stars 36 forks source link

Upgrade_71 travis failures (does not reproduce locally) #108

Open dalehenrich opened 8 years ago

dalehenrich commented 8 years ago

The following login error happens pretty regularly on Travis for the Upgrade_71 test, but does not reproduce locally:

!=========================================================================
topaz> ! Copyright (C) GemTalk Systems 1986-2016.  All Rights Reserved.
topaz> !
topaz> ! Name - upgradeImage.topaz
topaz> !
topaz> ! Purpose: 
topaz> !
topaz> !    Upgrade the image of a 3.x database to the current version.
topaz> !
topaz> ! $Id: upgradeImage.topaz 38383 2016-01-08 18:22:35Z lalmarod $
topaz> !
topaz> !=======================================================================
topaz> 
topaz> set gemstone $stoneName user SystemUser pass swordfish
topaz> !
topaz> display resultcheck
topaz> level 0
topaz> !
topaz> set INCONVERSION
topaz> expectvalue @268
topaz> ! this login will wait for symbolvm to commit its upgrade transaction
topaz> login
[Info]: User ID: SystemUser
[Info]: Repository: travis1_3.3.0
[Info]: Session ID: 5
[Info]: GCI Client Host: <Linked>
[Info]: Page server PID: -1
successful login
topaz 1> 
topaz 1> ! workaround 42294, relogin to get a view after the symbolvm first commit
topaz 1> logout
topaz> set INCONVERSION
topaz> expectvalue @268
topaz> login
-----------------------------------------------------
GemStone: Error         Fatal
The connection to the Stone Repository monitor was refused:
, 
Error Category: [GemStone] Number: 4136  Arg Count: 1
Arg 1: 20
ERROR: UNEXPECTED ERROR
dalehenrich commented 8 years ago

As of this build and this commit https://github.com/GsDevKit/GsDevKit_home/commit/4dcf446d9c08cd731565811d69eec555fee40133 Upgrade_71 is green

dalehenrich commented 5 years ago

I've seen this bug reproduce locally, however, I did not have enough logging present to see what the root cause was .. it does seem that the upgrade actually succeeded (in the local test case), but the script exited with a non-zero status ...