Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up failures/errors/sentButNotImplemented/undefinedSymbols for Travis-CI tests #8

Open
dalehenrich opened this issue Jan 27, 2017 · 5 comments

Comments

@dalehenrich
Copy link
Member

Tale of the tape from travis build:

screenshot - 01272017 - 01 13 41 pm

The unimplemented selectors are listed below as well as the undefined symbol:

Running suite "GemStone-3.3.3 Server (travis)" with 37 tests.
........E......................--transcript--'Sent but not implemented from #''SortedCollection>>join:'''
--transcript--'#''reSort'''
--transcript--'Sent but not implemented from #''MultiByteBinaryOrTextStream>>converter'''
--transcript--'#''defaultConverter'''
--transcript--'Sent but not implemented from #''UTF16TextConverter>>nextPutByteString:toStream:'''
--transcript--'#''basicNextPutAll:'''
--transcript--'Sent but not implemented from #''ByteTextConverterTest>>testLatin2ToUnicodeConversion'''
--transcript--'#''isWideString'''
F--transcript--'Undefined Symbol:#''Unicode'''
FFE.Finished running suite: GemStone-3.3.3 Server (travis)
@dalehenrich
Copy link
Member Author

@pdebruic, @jbrichau, @JupiterJones I can do a bit of the work, but I need to know which of these tests are important (including the sentButNotImplemented messages) ... I assume it is useful to be able use the travis build status to assess the validity of updates and pull requests?

@JupiterJones
Copy link
Contributor

Hi Dale,

I don't use any of those particular methods, however, I'm adding a bunch of stuff to PharoCompatibility at the moment to more easily support an updated Pillar and Pier3 so it would be great to have SmalltalkCI running.

@dalehenrich
Copy link
Member Author

@JupiterJones SmalltalkCI is now being used, just need to get to point where all tests pass ...

@jbrichau
Copy link
Member

@dalehenrich this repo never got out of the 'experimental' phase ;)
Let me save you some time and run over everything first, unless you have certain plans for this repo?
(I have not been following what is happening over the last year or so, and hope to reconnect and do some work, maybe this is a good starting point ;)

@dalehenrich
Copy link
Member Author

I have no explicit plans, but I saw that @JupiterJones was doing updates and that the travis tests were failing to load ... I've updated things so that smalltalkCI is being used and will let you guys take it from here:)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants