No reason of failure given about smalltalkci HOT 11 CLOSED

This happens if #directory : is missing from configuration STON.

First of all it would be nice to tell people if they are missing something.

Secondly, how about making #directory setting optional, and make it point to the root of the project by default?

from smalltalkci.

Thanks for reporting, @Uko. This is definitely a problem and I like your suggestion.
It actually reminds me of the fact that I should add more tests to SmalltalkCI and it's platform-specific packages.

from smalltalkci.

I'm having the same issue, and it's not #directory related as far as I can tell; all my builds are failing because of this.

.smalltalk.ston: https://github.com/dynacase/dynacase-model/blob/90146e44c497972ca8a81d3032068cc952705ad2/.smalltalk.ston

failing build: https://travis-ci.org/dynacase/dynacase-model/builds/111426018#L244

from smalltalkci.

Mh, this is bad news. I just run the dynacase build locally and it passes without any problems, so it's probably a Travis thing. Could you enable debugging output by overriding script in your .travis.yml:

script: $SMALLTALK_CI_HOME/run.sh --debug --verbose

from smalltalkci.

It's even worse: your tests seem to be passing now on Travis 🙈
What happens if you restart your older failing build?

from smalltalkci.

and now it's failing again… so verbose/debug is setting something wrong?

from smalltalkci.

--verbose is only used here, and --debug here. They are not used at all in pharo/run.sh.
So I really don't see why this is happening :(

from smalltalkci.

@peteruhnak and I have been able to identify and fix the problem.

Things I still need to do:

• Display meaningful error when SmalltalkCI runCIFor: is invoke with a non-STON file
• Make sure custom file is a STON file

from smalltalkci.

I have a related problem with a slightly different error condition for a pharo build where I see the following in the travis log where there is absolutely no information about why the load failed:

Loaded -> SmalltalkCI-Tests-dkh.21 --- filetree:///home/travis/build/dalehenrich/smalltalkCI/repository [:] --- cache
Loaded -> SmalltalkCI-Package-Tests-dkh.1 --- filetree:///home/travis/build/dalehenrich/smalltalkCI/repository [:] --- cache
Loaded -> SmalltalkCI-Package-Pharo-Tests-dkh.1 --- filetree:///home/travis/build/dalehenrich/smalltalkCI/repository [:] --- cache
Loaded -> SmalltalkCI-Excluded-Tests-fn.1 --- filetree:///home/travis/build/dalehenrich/smalltalkCI/repository [:] --- cache
Loaded -> STON-Tests-fn.54 --- filetree:///home/travis/build/dalehenrich/smalltalkCI/repository [:] --- cache
Failed to load and test project.
The command "$SMALLTALK_CI_HOME/run.sh --debug && $SMALLTALK_CI_HOME/tests/fail_test.sh" exited with 1.
Done. Your build exited with 1.

Fortunately, the squeak build is failing in the same spot and presumably has the same error:

Loaded -> SmalltalkCI-Tests-dkh.21 --- filetree:///home/travis/build/dalehenrich/smalltalkCI/repository [:] --- cache
Loaded -> SmalltalkCI-Excluded-Tests-fn.1 --- filetree:///home/travis/build/dalehenrich/smalltalkCI/repository [:] --- cache
(ZnBufferedReadStream is Undeclared) 
(ZnBufferedWriteStream is Undeclared) 
Loaded -> STON-Tests-fn.54 --- filetree:///home/travis/build/dalehenrich/smalltalkCI/repository [:] --- cache
...finished baselineSmalltalkCICategoryTest class>>sunitName
isAbstract
    "Override to true if a TestCase subclass is Abstract and should not
    have TestCase instances built from it"
    ^ self sunitName = #SmalltalkCIAbstractTest
SmalltalkCICategoryTest class(Object)>>doesNotUnderstand: #sunitName
SmalltalkCICategoryTest class(SmalltalkCIAbstractTest class)>>isAbstract
[] in SCITestReport class>>runClasses:named:
[] in Set>>select:
Set>>do:
Set>>select:
SCITestReport class>>runClasses:named:
SmalltalkCISqueak>>runTests

So it appears that pharo is not properly dumping the stack trace to the travis log ...

BTW, I can open a separate issue if you want ... the solution is probably different than this particular case

from smalltalkci.

I would usually run smalltalkCI locally with --headfull mode enabled. This will most likely show you a Pharo image with an open debugger. I'll have a look next week.

And feel free to open another issue if you think it's unrelated. :)

from smalltalkci.

Closed in favor of #115.

from smalltalkci.