CI job fix #16
Open
CI job fix #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pharo-vm-core changed to pharo5-vm-core. Executables and directories were also renamed to have pharo5- prefix
The dependency pharo-vm-core was replaced by pharo5-vm-core. Binaries' names have also changed
voyage-stable: zecke/voyage-stable:1.3.1-patch, mongotalk: zecke/mongotalk tag 1.9.5
|
Travis job summary: All tests passed. Job failed because the OBS_USER and OBS_PASS are not set |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I cloned the repo the travis job failed. I have been fixing it since then.
testWaitUntiltest doesn't pass still though when I run it from the image (which I get after osmo-smsc deb package installation) it passes.Last build job result: https://travis-ci.com/efistokl/smsc/builds/99782911
OBS repo: https://build.opensuse.org/package/show/home:efistokl:osmo-smsc:latest/osmo-smsc
The main problem was that the version of MongoTalk wasn't fixed. It was set just to the master branch of the repo pharo-nosql/mongotalk in the baseline.
Other things that caused "regression":
"sudo /opt/python/2.7.*/bin/python2 -m pip install -r ./integration-tests/requirements.txt"were not visible by integration test scriptsWhat I experience right now when I run the osmo-smsc is that it hangs when I try to add SS7 link via OM. (curl hangs as it doesn't get any response)
I will look for ways how to debug this stuff when I am done with my current task.