We are back to green again. Keep calm and carry on merging on green tests again
– Ivan
···
On Tue, Sep 12, 2017 at 9:45 PM, Ivan Necas wrote:
> Hi,
>
> We've pushed new version of foreman-tasks, that included the last
> piece of transition of Dynfow into the core. Unfortunately (or rather
> fortunately
> - better in CI than in production:) the Katello tests discovered one
> issue in the
> way the transition of the Dynflow initialization was made.
>
> It caused the Katello tests to fail on
>
> ActiveRecord::StatementInvalid: PG::ObjectInUse: ERROR: database
> "test_develop_pr_katello-2-test" is being accessed by other users
>
> For more details, see http://projects.theforeman.org/issues/20908
>
> The proposed fix to the foreman repo is here:
> https://github.com/theforeman/foreman/pull/4826/files
>
> Reviews more than welcome
>
> -- Ivan
One observation: it seems you need to rebase the foreman PRs in order
the change to be effective
in the tests.
– Ivan
···
On Wed, Sep 13, 2017 at 3:35 PM, Ivan Necas wrote:
> We are back to green again. Keep calm and carry on merging on green tests again
>
> -- Ivan
>
> On Tue, Sep 12, 2017 at 9:45 PM, Ivan Necas wrote:
>> Hi,
>>
>> We've pushed new version of foreman-tasks, that included the last
>> piece of transition of Dynfow into the core. Unfortunately (or rather
>> fortunately
>> - better in CI than in production:) the Katello tests discovered one
>> issue in the
>> way the transition of the Dynflow initialization was made.
>>
>> It caused the Katello tests to fail on
>>
>> ActiveRecord::StatementInvalid: PG::ObjectInUse: ERROR: database
>> "test_develop_pr_katello-2-test" is being accessed by other users
>>
>> For more details, see http://projects.theforeman.org/issues/20908
>>
>> The proposed fix to the foreman repo is here:
>> https://github.com/theforeman/foreman/pull/4826/files
>>
>> Reviews more than welcome
>>
>> -- Ivan