search

GsDevKit / GsDevKit_home

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

GEMSTONE_NRS_ALL semantics have (apparently) changed for 3.5.3 and appear to interfere with gci logins for Seaside builds #288

Closed dalehenrich closed 4 years ago

dalehenrich commented 4 years ago

during 3.5.3 test runs, I'm consistently getting the following UNEXPECTED ERROR attempting to login to server:

startnetldi[Info]: GemStone version '3.5.3'
startnetldi[Info]: Starting GemStone network server 'fgsd_gsdevkitSeaside32Tests8476stone1_ldi'.
startnetldi[Info]: GEMSTONE is: '/secure/users/dhenrich/work/h_35x_tests/batt/GsDevKit_home-gsd_gsdevkitSeaside32Tests-0708-160743/server/stones/fgsd_gsdevkitSeaside32Tests8476stone1/product'.
startnetldi[Info]: GEMSTONE_NRS_ALL is: '#dir:$GEMSTONE_LOGDIR#log:%N%P.log'.
startnetldi[Info]: Log file is '/secure/users/dhenrich/work/h_35x_tests/batt/GsDevKit_home-gsd_gsdevkitSeaside32Tests-0708-160743/server/stones/fgsd_gsdevkitSeaside32Tests8476stone1/logs/netldi.log'.
startnetldi[Info]: GemStone server 'fgsd_gsdevkitSeaside32Tests8476stone1_ldi' has been started, process 11834

...finished :: startNetldi fgsd_gsdevkitSeaside32Tests8476stone1
...finished :: startStone -b fgsd_gsdevkitSeaside32Tests8476stone1

tode > # after test run, <self> will be a TestResult
nil
tode > project install --url=http://gsdevkit.github.io/GsDevKit_home/Seaside32.stonError:  For further information about login failures, check the gem log file
TDTopezGemStoneClient>>loginUsing:
TDTopezGemStoneClient>>login
TDTopezGemStoneClient>>session
TDTopezGemStoneClient>>evaluateCommand:batchMode: in Block: [ ...
BlockClosure>>ensure:
TDTopezGemStoneClient>>evaluateCommand:batchMode:
TDShell>>evaluateCommand:batchMode:
TDShell>>evaluate:batchMode: in Block: [ :command | result := self evaluateCommand: comma...etc...
TDCommandLine class>>line:forEachCommand: in Block: [ :isolated | ...
OrderedCollection>>do:
TDCommandLine class>>line:forEachCommand:
TDCommandLine class>>fromStream:selectLine:forEachCommand: in Block: [ :cmdLine | ...
OrderedCollection>>do:
TDCommandLine class>>fromStream:selectLine:forEachCommand:
TDShell>>evaluate:batchMode: in Block: evaluate: aString batchMode: aBool...
BlockClosure>>on:do:
TDShell>>evaluate:batchMode:
TDShell>>evaluate:
GsDevKitTodeItCommandLineHandler>>evaluate: in Block: [ :line | ...
ByteString(String)>>linesDo: in Block: [ :start :endWithoutDelimiters :end | aBlock value...etc...
ByteString(String)>>lineIndicesDo:
ByteString(String)>>linesDo:
GsDevKitTodeItCommandLineHandler>>evaluate:
GsDevKitTodeItCommandLineHandler>>evaluate
GsDevKitTodeItCommandLineHandler>>activate in Block: [ self evaluate ]
BlockClosure>>ensure:
Author>>useAuthor:during:
Author class>>useAuthor:during:
GsDevKitTodeItCommandLineHandler>>activate
GsDevKitTodeItCommandLineHandler class(CommandLineHandler class)>>activateWith:
Error on or near line 99 :: devKitCommandLine todeIt fgsd_gsdevkitSeaside32Tests8476stone1 :: devKitCommandLine todeIt fgsd_gsdevkitSeaside32Tests8476stone1
UNEXPECTED ERROR: .....
=======================
Test complete
=======================
dalehenrich commented 4 years ago

At the end of the day, this does not appear to be an issue ... I had to go through the rigamarole of pushing to master in order to test against a 3.5.3 build (not yet released) and it is not the root cause of the problem I observed ... I will back out these changes