-
Notifications
You must be signed in to change notification settings - Fork 94
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
Foreman 1.17 updates #297
Foreman 1.17 updates #297
Conversation
includes GH-295 |
Tests running here http://ci.theforeman.org/job/test_plugin_pull_request/4459/ |
this will fail until http://theforeman.org/issues/22065 is resolved. |
theforeman/foreman#5146 got in, tests running here http://ci.theforeman.org/job/test_plugin_pull_request/4460/ |
@mmoll The tests are failing a lot :/ |
Could that be this related to GH-298? Or rather the underlying core changes for it? |
Doesn't seem to be related in any way |
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
Running the jenkins, just to see what the issue is now http://ci.theforeman.org/job/test_plugin_pull_request/4483/ |
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
down to |
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
http://ci.theforeman.org/job/test_plugin_pull_request/4497/ - the builds that came back are green now, but the hangs are like the ones seen with foreman-tasks tests. |
I was able to track the the stuck issue down to https://github.com/theforeman/foreman/blob/8c2262ac78c05dc2b3f723d43ba780b468d27b19/app/jobs/create_rss_notifications.rb#L8 - My guess is some dead-lock with rails loading when running from different thread: the solution will be not to trigger the rss checker in tests, but need to spend some more time on that. |
This I guess will be the issue at least in foreman-tasks, still not sure if that affects remote execution as well |
There were the following issues with the commit message:
If you don't have a ticket number, please create an issue in Redmine. More guidelines are available in Coding Standards or on the Foreman wiki. This message was auto-generated by Foreman's prprocessor |
💚 |
@iNecas anything to add here or can we get this in? |
It seems that the |
No description provided.