Reuse Channels#10332
Conversation
|
Test FAILed. |
|
Closing and re-opening to trigger another jenkins build, we need it to download the remote logs. |
|
Test FAILed. |
|
Left it running overnight on my dev box here and still running with no exceptions, anything interesting from the logs? |
|
ok, we need your versions report, |
|
Hopefully this is helpful :/ if it helps at all it also works on my fedora tower at home. Below is the output from my work machine (rhel 6) |
|
Here's what I'm getting https://gist.github.com/s0undt3ch/456a8a0b0c9154e29d1e |
|
|
If you have a chance to get |
|
Ok, i have it failing on some local tests now-- i think i may even have it fixed! Just running a few more tests locally. |
|
Awesome! |
|
In the unittest framework it creates the master and a few minions on the same pid, so my cache key wasn't "unique". It looks like most of the tests pass now-- going to get a merge build going to see :) |
|
Test FAILed. |
|
Test FAILed. |
|
K, just pushed update for pep8 test-- but the rest of the tests passed so i expect this next run to pass :) |
|
Test FAILed. |
|
Test FAILed. |
|
Test FAILed. |
|
The tests seem to have failed again? (they are grey not red or green...) if so, any details on why its failing? |
|
Gray is bad, and if there are no logs, the remote minion is not working, kind of similar to the previous problem? |
|
Hmm, I'll have to mess with it some more. This problem is actually harder
|
|
Thanks @jacksontj, If we can get this working it will really speed things up! |
|
Test FAILed. |
|
Test FAILed. |
|
Test FAILed. |
|
Test FAILed. |
|
Thanks. We can merge this once we clean up the test suite and see how it is! |
|
Yea, i'm just waiting on a clean develop to rebase onto so i can get this test suite to run :/ |
|
Test FAILed. |
|
Unless I'm misreading it looks like the tests passed with an error about
|
|
Nope, the build aborted. If you rebase to current develop, you should get a better notion of what's going on since current develop seems to be building properly on PR's. |
with support for multiple ttypes Submitting merge request to get jenkins run. Last time this was merged there were some problems which seem to be related to this but i'm unable to reproduce them locally-- so hopefully we can get something from Jenkins :)
|
Test FAILed. |
|
Ah Ha! The tests passed and the only issue Jenkins is complaining is a lint error which is unrelated to your PR. @thatch45 this PR seems ready for another review. @jacksontj agreed? |
|
@s0undt3ch This looks good to go! 👍 |
|
Now to see if all of the platforms stay blue! (well, the ones that are blue...) |
|
The tests are all timing out... |
|
Weird.... How did it pass before?
|
|
Thats what I am wondering, I am going to revert it so we can get the tests going again |
|
Yep, they are coming back after the revert, sorry @jacksontj ... |
|
Any logs or ideas why it was failing? Hard for me to debug when all tests
|
|
@thatch45 did we ever figure out why this was failing? |
|
@thatch45 ping :) |
|
@thatch45 ping again, this will make a big difference in our load/latency numbers. I just need to know why this failed so I can fix it |
|
Sorry I missed you here. We were running into strange conditions. Maybe we should make it a configuration option for now? |
|
Sure I can set that up, when would we be able to change the default option On Tue, May 27, 2014 at 2:26 PM, Thomas S Hatch notifications@github.comwrote:
|
|
I think we should make it configurable and then change the default for the Lithium release right after we cut the RC for Helium, so we have a good long time to sort out the hicups |
|
Sounds good, I'll put together a pull req this week.
|
…annel object. This is an improvement over saltstack#10332 in that you don't have to worry about someone creating a ZeroMQChannel then forking (thereby breaking the thread-pid rules). This way once it moves it will create a new sreq as needed. This is possible now that saltstack#13155 is merged
with support for multiple ttypes
Submitting merge request to get jenkins run. Last time this was merged there were some problems which seem to be related to this but i'm unable to reproduce them locally-- so hopefully we can get something from Jenkins :)