Project

General

Profile

Actions

Bug #17575

open

"Failed importing of report" error printed to stderr when running tests

Added by Dominic Cleal about 8 years ago. Updated about 8 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Tests
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When running rake test, the following is printed:

[2016-12-05 11:10:55.593 #22846] ERROR --  action: Failed importing of report: custom string (RuntimeError)
/home/dcleal/code/foreman/foreman/app/services/actions/foreman/report/import.rb:17:in `run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action.rb:506:in `block (3 levels) in execute_run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/middleware/stack.rb:26:in `pass'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/middleware.rb:17:in `pass'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action/progress.rb:30:in `with_progress_calculation'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action/progress.rb:16:in `run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/middleware/stack.rb:22:in `call'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/middleware/world.rb:30:in `execute'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action.rb:505:in `block (2 levels) in execute_run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action.rb:504:in `catch'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action.rb:504:in `block in execute_run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action.rb:419:in `block in with_error_handling'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action.rb:419:in `catch'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action.rb:419:in `with_error_handling'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action.rb:499:in `execute_run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/action.rb:260:in `execute'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/dynflow-0.8.17/lib/dynflow/testing/factories.rb:73:in `run_action'
/home/dcleal/code/foreman/foreman/test/unit/actions/report/import_test.rb:31:in `block (3 levels) in <class:ImportTest>'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest/assertions.rb:293:in `assert_raises'
/home/dcleal/code/foreman/foreman/test/unit/actions/report/import_test.rb:31:in `block (2 levels) in <class:ImportTest>'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest/test.rb:106:in `block (3 levels) in run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest/test.rb:204:in `capture_exceptions'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest/test.rb:103:in `block (2 levels) in run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest/test.rb:256:in `time_it'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest/test.rb:102:in `block in run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:317:in `on_signal'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest/test.rb:276:in `with_info_handler'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest/test.rb:101:in `run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:759:in `run_one_method'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:293:in `run_one_method'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:287:in `block (2 levels) in run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:286:in `each'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:286:in `block in run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:317:in `on_signal'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:306:in `with_info_handler'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:285:in `run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:149:in `block in __run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:149:in `map'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:149:in `__run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:126:in `run'
/home/dcleal/.rvm/gems/ruby-2.3.0@foreman/gems/minitest-5.1.0/lib/minitest.rb:55:in `block in autorun'

Tests should be silent, the error should be caught/logged somewhere.


Related issues 1 (0 open1 closed)

Related to Foreman - Feature #15779: Make report, puppet classes and environments importing asynchronous using foreman-tasksClosedMarek Hulán07/22/2016Actions
Actions #1

Updated by Dominic Cleal about 8 years ago

  • Priority changed from Normal to Low
Actions #2

Updated by Dominic Cleal about 8 years ago

  • Related to Feature #15779: Make report, puppet classes and environments importing asynchronous using foreman-tasks added
Actions

Also available in: Atom PDF