-
Notifications
You must be signed in to change notification settings - Fork 22
Do a fresh merge from master for genome. #160
Comments
Known or expected sources of issues
|
Reposting here for @mkiwala-g "Nessy is the new locking service, and Ptero is the replacement for workflow. GMS is not dependent on either of these systems at this time, so merging in the latest master should not make sGMS dependent on these new systems." |
Ah interesting. So "genome model build start" won't run into any problems in a world I won't claim to understand, but glad if it's going to be that easy. On Fri, Feb 20, 2015 at 9:02 AM, Jason Walker [email protected]
|
The The changes were pretty minimal. I made I also merged the latest UR and tagged it as Workflow is a little more weird. The latest master has Oracle passwords in it. I'm presuming Oracle isn't being used anymore, and that if it is these aren't real. Is the workflow repo that is actually used somewhere else now? |
I pushed up a new |
Since the sGMS installer, automatically pulls from |
We can rename those branches. I'll do that. Sent from my iPhone
|
There does seem to be an error related to resource locking on attempt to prime the database now: #162 |
So I renamed the branches. The old regular gms-pub branches are back where they were. The new install in the So to test the new hypothetical merge:
|
These branches are still being tested, to test this branch do the same as above,
|
This will entail getting a bunch of new software related to workflow, nessy, and other things.
The text was updated successfully, but these errors were encountered: