sidekiq failures

gistfile1.txt

Failures:

  1) Javascript tracker 
  When clients install javascript on their site, it should send us events
 sends a page event for the current session
     Failure/Error: wait_until { @session = mongo.sessions.find_one }
     Capybara::TimeoutError:
       timed out
     # ./spec/acceptance/javascript_tracker_spec.rb:14:in `find_session'
     # ./spec/acceptance/javascript_tracker_spec.rb:26:in `block (2 levels) in <top (required)>'

  2) Javascript tracker 
  When clients install javascript on their site, it should send us events
 sends custom event for the current session
     Failure/Error: wait_until { @session = mongo.sessions.find_one }
     Capybara::TimeoutError:
       timed out
     # ./spec/acceptance/javascript_tracker_spec.rb:14:in `find_session'
     # ./spec/acceptance/javascript_tracker_spec.rb:18:in `block in find_session_with'
     # ./spec/acceptance/javascript_tracker_spec.rb:18:in `find_session_with'
     # ./spec/acceptance/javascript_tracker_spec.rb:38:in `block (2 levels) in <top (required)>'

  3) Javascript tracker 
  When clients install javascript on their site, it should send us events
 sends custom event with attributes for the current session
     Failure/Error: wait_until { @session = mongo.sessions.find_one }
     Capybara::TimeoutError:
       timed out
     # ./spec/acceptance/javascript_tracker_spec.rb:14:in `find_session'
     # ./spec/acceptance/javascript_tracker_spec.rb:18:in `block in find_session_with'
     # ./spec/acceptance/javascript_tracker_spec.rb:18:in `find_session_with'
     # ./spec/acceptance/javascript_tracker_spec.rb:49:in `block (2 levels) in <top (required)>'

  4) Javascript tracker 
  When clients install javascript on their site, it should send us events
 logged in user creates a customer record with customers info
     Failure/Error: wait_until { @customer = mongo.customers.find_one(_id: id.to_s) }
     Capybara::TimeoutError:
       timed out
     # ./spec/acceptance/javascript_tracker_spec.rb:9:in `find_customer'
     # ./spec/acceptance/javascript_tracker_spec.rb:65:in `block (3 levels) in <top (required)>'

  5) Logs 
  Clients should be able to see a stream of events they are tracking
 Customer hasnt been identified Clients see unidentified events
     Failure/Error: page.should have_content("customer with id: 1 special_event")
       expected there to be content "customer with id: 1 special_event" in "Help Account Logout user57@example.com Production EMAIL Campaigns Layouts CUSTOMERS Segments Customer Profiles ADMIN Logs Tracking Code Logs Production Ancient Proverb: He who sends no data shall have no logs. 2012 Peaberry Software Inc."
     # ./spec/acceptance/logs_spec.rb:24:in `block (3 levels) in <top (required)>'

  6) Logs 
  Clients should be able to see a stream of events they are tracking
 Customer has been identified Clients see the latest events and attributes
     Failure/Error: page.should have_content("customer@example.com filter special_event")
       expected there to be content "customer@example.com filter special_event" in "Help Account Logout user58@example.com Production EMAIL Campaigns Layouts CUSTOMERS Segments Customer Profiles ADMIN Logs Tracking Code Logs Production Ancient Proverb: He who sends no data shall have no logs. 2012 Peaberry Software Inc."
     # ./spec/acceptance/logs_spec.rb:37:in `block (3 levels) in <top (required)>'

  7) Logs 
  Clients should be able to see a stream of events they are tracking
 Customer has been identified Clients can see when attributes change
     Failure/Error: page.should have_content("customer@example.com filter name")
       expected there to be content "customer@example.com filter name" in "Help Account Logout user59@example.com Production EMAIL Campaigns Layouts CUSTOMERS Segments Customer Profiles ADMIN Logs Tracking Code Logs Production Ancient Proverb: He who sends no data shall have no logs. 2012 Peaberry Software Inc."
     # ./spec/acceptance/logs_spec.rb:54:in `block (3 levels) in <top (required)>'

  8) Logs 
  Clients should be able to see a stream of events they are tracking
 Customer has been identified Clients can search for events and attributes by a given customer
     Failure/Error: fill_in "email", with: "customer@example.com"
     Capybara::ElementNotFound:
       cannot fill in, no text field, text area or password field with id, name, or label 'email' found
     # (eval):2:in `fill_in'
     # ./spec/acceptance/logs_spec.rb:68:in `block (3 levels) in <top (required)>'

  9) Logs 
  Clients should be able to see a stream of events they are tracking
 Customer has been identified Clients can click on an email address to search for a given customer
     Failure/Error: click_link "filter"
     Capybara::ElementNotFound:
       no link with title, id or text 'filter' found
     # (eval):2:in `click_link'
     # ./spec/acceptance/logs_spec.rb:82:in `block (3 levels) in <top (required)>'

  10) Edit output 
  Users should be able to edit the output and the email their output sends
 Users can edit an existing output
     Failure/Error: page.should have_css(".btn.disabled", text: "Saved!")
       expected css ".btn.disabled" with text "Saved!" to return something
     # ./spec/acceptance/outputs/edit_spec.rb:19:in `block (2 levels) in <top (required)>'

  11) Edit output 
  Users should be able to edit the output and the email their output sends
 User can preview the email
     Failure/Error: fill_in "email_subject", with: "Why haven't you visited lately?"
     Capybara::ElementNotFound:
       cannot fill in, no text field, text area or password field with id, name, or label 'email_subject' found
     # (eval):2:in `fill_in'
     # ./spec/acceptance/outputs/edit_spec.rb:37:in `block (2 levels) in <top (required)>'

  12) Edit output 
  Users should be able to edit the output and the email their output sends
 User can send themselves a test email without rendering liquid variables
     Failure/Error: fill_in "email_subject", with: "Hi {{ customer.name }}"
     Capybara::ElementNotFound:
       cannot fill in, no text field, text area or password field with id, name, or label 'email_subject' found
     # (eval):2:in `fill_in'
     # ./spec/acceptance/outputs/edit_spec.rb:48:in `block (2 levels) in <top (required)>'

  13) Edit output 
  Users should be able to edit the output and the email their output sends
 Can set a layout for an email
     Failure/Error: click_link "Emails"
     Capybara::ElementNotFound:
       no link with title, id or text 'Emails' found
     # (eval):2:in `click_link'
     # ./spec/acceptance/outputs/edit_spec.rb:66:in `block (2 levels) in <top (required)>'

  14) Edit output 
  Users should be able to edit the output and the email their output sends
 Users are informed how to send custom variables if they havent
     Failure/Error: page.body.should =~ /You haven't sent us any user attributes/
       expected: /You haven't sent us any user attributes/
            got: "<!DOCTYPE html><html><head><meta charset=\"UTF-8\"><style type=\"text/css\">html             { height: 100%; }\nbody             { min-height: 100%; padding: 0; margin: 0; margin-top: -1px; padding-top: 1px; }\n._wysihtml5-temp { display: none; }\nbody.placeholder { color: #a9a9a9 !important; }\nbody[disabled]   { background-color: #eee !important; color: #999 !important; cursor: default !important; }\nimg:-moz-broken  { -moz-force-broken-image-icon: 1; height: 24px; width: 24px; }</style></head><body marginwidth=\"0\" marginheight=\"0\" contenteditable=\"true\" class=\"ember-view ember-text-area span9 wysihtml5-editor\" spellcheck=\"true\" style=\"background-color: rgb(255, 255, 255); color: rgb(85, 85, 85); cursor: auto; font-family: Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; line-height: 18px; letter-spacing: normal; text-align: -webkit-auto; text-decoration: none; text-indent: 0px; text-rendering: auto; word-break: normal; word-wrap: break-word; word-spacing: 0px; \">Insert content here</body></html>" (using =~)
       Diff:
       @@ -1,2 +1,7 @@
       -/You haven't sent us any user attributes/
       +<!DOCTYPE html><html><head><meta charset="UTF-8"><style type="text/css">html             { height: 100%; }
       +body             { min-height: 100%; padding: 0; margin: 0; margin-top: -1px; padding-top: 1px; }
       +._wysihtml5-temp { display: none; }
       +body.placeholder { color: #a9a9a9 !important; }
       +body[disabled]   { background-color: #eee !important; color: #999 !important; cursor: default !important; }
       +img:-moz-broken  { -moz-force-broken-image-icon: 1; height: 24px; width: 24px; }</style></head><body marginwidth="0" marginheight="0" contenteditable="true" class="ember-view ember-text-area span9 wysihtml5-editor" spellcheck="true" style="background-color: rgb(255, 255, 255); color: rgb(85, 85, 85); cursor: auto; font-family: Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; line-height: 18px; letter-spacing: normal; text-align: -webkit-auto; text-decoration: none; text-indent: 0px; text-rendering: auto; word-break: normal; word-wrap: break-word; word-spacing: 0px; ">Insert content here</body></html>
     # ./spec/acceptance/outputs/edit_spec.rb:93:in `block (2 levels) in <top (required)>'

  15) Edit output 
  Users should be able to edit the output and the email their output sends
 Users can view the custom variables they can use in their email
     Failure/Error: page.body.should =~ /Use this syntax to embed any of these attributes in your emails/
       expected: /Use this syntax to embed any of these attributes in your emails/
            got: "<!DOCTYPE html><html><head><meta charset=\"UTF-8\"><style type=\"text/css\">html             { height: 100%; }\nbody             { min-height: 100%; padding: 0; margin: 0; margin-top: -1px; padding-top: 1px; }\n._wysihtml5-temp { display: none; }\nbody.placeholder { color: #a9a9a9 !important; }\nbody[disabled]   { background-color: #eee !important; color: #999 !important; cursor: default !important; }\nimg:-moz-broken  { -moz-force-broken-image-icon: 1; height: 24px; width: 24px; }</style></head><body marginwidth=\"0\" marginheight=\"0\" contenteditable=\"true\" class=\"ember-view ember-text-area span9 wysihtml5-editor\" spellcheck=\"true\" style=\"background-color: rgb(255, 255, 255); color: rgb(85, 85, 85); cursor: auto; font-family: Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; line-height: 18px; letter-spacing: normal; text-align: -webkit-auto; text-decoration: none; text-indent: 0px; text-rendering: auto; word-break: normal; word-wrap: break-word; word-spacing: 0px; \">Insert content here</body></html>" (using =~)
       Diff:
       @@ -1,2 +1,7 @@
       -/Use this syntax to embed any of these attributes in your emails/
       +<!DOCTYPE html><html><head><meta charset="UTF-8"><style type="text/css">html             { height: 100%; }
       +body             { min-height: 100%; padding: 0; margin: 0; margin-top: -1px; padding-top: 1px; }
       +._wysihtml5-temp { display: none; }
       +body.placeholder { color: #a9a9a9 !important; }
       +body[disabled]   { background-color: #eee !important; color: #999 !important; cursor: default !important; }
       +img:-moz-broken  { -moz-force-broken-image-icon: 1; height: 24px; width: 24px; }</style></head><body marginwidth="0" marginheight="0" contenteditable="true" class="ember-view ember-text-area span9 wysihtml5-editor" spellcheck="true" style="background-color: rgb(255, 255, 255); color: rgb(85, 85, 85); cursor: auto; font-family: Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; line-height: 18px; letter-spacing: normal; text-align: -webkit-auto; text-decoration: none; text-indent: 0px; text-rendering: auto; word-break: normal; word-wrap: break-word; word-spacing: 0px; ">Insert content here</body></html>
     # ./spec/acceptance/outputs/edit_spec.rb:103:in `block (2 levels) in <top (required)>'

  16) Edit output 
  Users should be able to edit the output and the email their output sends
 Users can delete an existing output
     Failure/Error: click_link "Delete Email"
     Capybara::ElementNotFound:
       no link with title, id or text 'Delete Email' found
     # (eval):2:in `click_link'
     # ./spec/acceptance/outputs/edit_spec.rb:116:in `block (3 levels) in <top (required)>'
     # ./spec/acceptance/support/helpers.rb:10:in `handle_js_confirm'
     # ./spec/acceptance/outputs/edit_spec.rb:115:in `block (2 levels) in <top (required)>'

  17) Manage triggers 
  Users should be view and interact with their triggers
 Users can create a new trigger
     Failure/Error: page.should have_css("#editCampaign")
       expected css "#editCampaign" to return something
     # ./spec/acceptance/triggers/manage_spec.rb:25:in `block (2 levels) in <top (required)>'

  18) Manage triggers 
  Users should be view and interact with their triggers
 Users can navigate to a specific output
     Failure/Error: page.should have_css('h1', text: output.name)
       expected css "h1" with text "Output75" to return something
     # ./spec/acceptance/triggers/manage_spec.rb:244:in `block (2 levels) in <top (required)>'

  19) Trigger report 
  Users should be able to view metrics about their trigger
 Clients can click on an email address to see a given customers activity
     Failure/Error: page.find('h1', :text => "customer1@example.com")
     Capybara::ElementNotFound:
       Unable to find css "h1"
     # (eval):2:in `find'
     # ./spec/acceptance/triggers/report_spec.rb:157:in `block (2 levels) in <top (required)>'

  20) Api::V1::CustomersController it sets email and data for the customer
     Failure/Error: customer.email.should == "customer@example.com"
       expected: "customer@example.com"
            got: nil (using ==)
     # ./spec/controllers/api/v1/customers_controller_spec.rb:28:in `block (2 levels) in <top (required)>'

  21) Api::V1::CustomersController it identifies the customer's default session
     Failure/Error: customer.default_session.identity.should == "5"
       expected: "5"
            got: nil (using ==)
     # ./spec/controllers/api/v1/customers_controller_spec.rb:38:in `block (2 levels) in <top (required)>'

  22) Api::V1::EventsController adds event to the customer's event list
     Failure/Error: }]
       expected: [{"type"=>"event", "name"=>"EventA", "data"=>{"key"=>"val"}, "timestamp"=>#<RSpec::Mocks::ArgumentMatchers::AnyArgMatcher:0x007fbda73767e0>}]
            got: [] (using ==)
       Diff:
       @@ -1,6 +1,2 @@
       -[{"type"=>"event",
       -  "name"=>"EventA",
       -  "data"=>{"key"=>"val"},
       -  "timestamp"=>
       -   #<RSpec::Mocks::ArgumentMatchers::AnyArgMatcher:0x007fbda73767e0>}]
       +[]
     # ./spec/controllers/api/v1/events_controller_spec.rb:38:in `block (2 levels) in <top (required)>'

  23) EventsController finds a session for the site and session uuid
     Failure/Error: Events::Session.should_receive(:new).with(Environment.first, params[:s])
       (<Events::Session (class)>).new(#<Environment id: 1, user_id: 1, name: "Production", site_id: "6a3e89dfb5e9b0b0b54a", api_key: "c82f79583fd61d58a7e3", created_at: "2012-10-17 17:01:27", updated_at: "2012-10-17 17:01:27">, "123456...")
           expected: 1 time
           received: 0 times
     # ./spec/controllers/events_controller_spec.rb:42:in `block (2 levels) in <top (required)>'

  24) EventsController adds event to the session's event list
     Failure/Error: session.should_receive(:add_event).with(event, false)
       (Mock "Session").add_event(#<Events::Event:0x007fbda7597268 @attributes={"type"=>"page", "name"=>"/", "data"=>{"key"=>"val"}}>, false)
           expected: 1 time
           received: 0 times
     # ./spec/controllers/events_controller_spec.rb:48:in `block (2 levels) in <top (required)>'

  25) EventsController identifies the session if event type is identify
     Failure/Error: session.should_receive(:identify).with("5")
       (Mock "Session").identify("5")
           expected: 1 time
           received: 0 times
     # ./spec/controllers/events_controller_spec.rb:54:in `block (2 levels) in <top (required)>'

  26) Segment save sends an email to admins notifying them of the update
     Failure/Error: current_email.should have_subject("Segment changed: triggers in need of updating")
       expected the subject to be "Segment changed: triggers in need of updating" but was "(NO_SUB) Segment changed: triggers in need of updating"
     # ./spec/models/segment_spec.rb:60:in `block (3 levels) in <top (required)>'

  27) Trigger.save segment_groups was updated sends an email to admins notifying them of the update
     Failure/Error: current_email.should have_subject("Trigger conditions changed: call in the MapReduce marines")
       expected the subject to be "Trigger conditions changed: call in the MapReduce marines" but was "(NO_SUB) Trigger conditions changed: call in the MapReduce marines"
     # ./spec/models/trigger_spec.rb:51:in `block (4 levels) in <top (required)>'

Finished in 870.9 seconds
602 examples, 27 failures, 3 pending

Failed examples:

rspec ./spec/acceptance/javascript_tracker_spec.rb:23 # Javascript tracker 
  When clients install javascript on their site, it should send us events
 sends a page event for the current session
rspec ./spec/acceptance/javascript_tracker_spec.rb:34 # Javascript tracker 
  When clients install javascript on their site, it should send us events
 sends custom event for the current session
rspec ./spec/acceptance/javascript_tracker_spec.rb:45 # Javascript tracker 
  When clients install javascript on their site, it should send us events
 sends custom event with attributes for the current session
rspec ./spec/acceptance/javascript_tracker_spec.rb:64 # Javascript tracker 
  When clients install javascript on their site, it should send us events
 logged in user creates a customer record with customers info
rspec ./spec/acceptance/logs_spec.rb:20 # Logs 
  Clients should be able to see a stream of events they are tracking
 Customer hasnt been identified Clients see unidentified events
rspec ./spec/acceptance/logs_spec.rb:33 # Logs 
  Clients should be able to see a stream of events they are tracking
 Customer has been identified Clients see the latest events and attributes
rspec ./spec/acceptance/logs_spec.rb:48 # Logs 
  Clients should be able to see a stream of events they are tracking
 Customer has been identified Clients can see when attributes change
rspec ./spec/acceptance/logs_spec.rb:64 # Logs 
  Clients should be able to see a stream of events they are tracking
 Customer has been identified Clients can search for events and attributes by a given customer
rspec ./spec/acceptance/logs_spec.rb:78 # Logs 
  Clients should be able to see a stream of events they are tracking
 Customer has been identified Clients can click on an email address to search for a given customer
rspec ./spec/acceptance/outputs/edit_spec.rb:13 # Edit output 
  Users should be able to edit the output and the email their output sends
 Users can edit an existing output
rspec ./spec/acceptance/outputs/edit_spec.rb:32 # Edit output 
  Users should be able to edit the output and the email their output sends
 User can preview the email
rspec ./spec/acceptance/outputs/edit_spec.rb:43 # Edit output 
  Users should be able to edit the output and the email their output sends
 User can send themselves a test email without rendering liquid variables
rspec ./spec/acceptance/outputs/edit_spec.rb:63 # Edit output 
  Users should be able to edit the output and the email their output sends
 Can set a layout for an email
rspec ./spec/acceptance/outputs/edit_spec.rb:88 # Edit output 
  Users should be able to edit the output and the email their output sends
 Users are informed how to send custom variables if they havent
rspec ./spec/acceptance/outputs/edit_spec.rb:96 # Edit output 
  Users should be able to edit the output and the email their output sends
 Users can view the custom variables they can use in their email
rspec ./spec/acceptance/outputs/edit_spec.rb:109 # Edit output 
  Users should be able to edit the output and the email their output sends
 Users can delete an existing output
rspec ./spec/acceptance/triggers/manage_spec.rb:17 # Manage triggers 
  Users should be view and interact with their triggers
 Users can create a new trigger
rspec ./spec/acceptance/triggers/manage_spec.rb:238 # Manage triggers 
  Users should be view and interact with their triggers
 Users can navigate to a specific output
rspec ./spec/acceptance/triggers/report_spec.rb:146 # Trigger report 
  Users should be able to view metrics about their trigger
 Clients can click on an email address to see a given customers activity
rspec ./spec/controllers/api/v1/customers_controller_spec.rb:26 # Api::V1::CustomersController it sets email and data for the customer
rspec ./spec/controllers/api/v1/customers_controller_spec.rb:36 # Api::V1::CustomersController it identifies the customer's default session
rspec ./spec/controllers/api/v1/events_controller_spec.rb:31 # Api::V1::EventsController adds event to the customer's event list
rspec ./spec/controllers/events_controller_spec.rb:41 # EventsController finds a session for the site and session uuid
rspec ./spec/controllers/events_controller_spec.rb:46 # EventsController adds event to the session's event list
rspec ./spec/controllers/events_controller_spec.rb:53 # EventsController identifies the session if event type is identify
rspec ./spec/models/segment_spec.rb:52 # Segment save sends an email to admins notifying them of the update
rspec ./spec/models/trigger_spec.rb:47 # Trigger.save segment_groups was updated sends an email to admins notifying them of the update
rake aborted!
/Users/ashaegupta/.rbenv/versions/1.9.3-p194-perf/bin/ruby -S rspec ./spec/acceptance/account_spec.rb ./spec/acceptance/admin/authentication_spec.rb ./spec/acceptance/admin/email_templates_spec.rb ./spec/acceptance/admin/emails_spec.rb ./spec/acceptance/admin/masquerade_spec.rb ./spec/acceptance/admin/outputs_spec.rb ./spec/acceptance/admin/plans_spec.rb ./spec/acceptance/admin/processing_triggers_spec.rb ./spec/acceptance/admin/triggers_spec.rb ./spec/acceptance/admin/users_spec.rb ./spec/acceptance/authentication_spec.rb ./spec/acceptance/conversion_spec.rb ./spec/acceptance/delete_spec.rb ./spec/acceptance/documentation_spec.rb ./spec/acceptance/email_layouts_spec.rb ./spec/acceptance/emails_spec.rb ./spec/acceptance/javascript_tracker_spec.rb ./spec/acceptance/logs_spec.rb ./spec/acceptance/onboarding_spec.rb ./spec/acceptance/outputs/edit_spec.rb ./spec/acceptance/segments_spec.rb ./spec/acceptance/transactional_emails_spec.rb ./spec/acceptance/triggers/manage_spec.rb ./spec/acceptance/triggers/processing_spec.rb ./spec/acceptance/triggers/report_spec.rb ./spec/acceptance/unsubscribe_spec.rb ./spec/controllers/api/v1/customers_controller_spec.rb ./spec/controllers/api/v1/events_controller_spec.rb ./spec/controllers/api_controller_spec.rb ./spec/controllers/application_controller_spec.rb ./spec/controllers/events_controller_spec.rb ./spec/controllers/masquerades_controller_spec.rb ./spec/controllers/sendgrid/events_controller_spec.rb ./spec/controllers/stripe/events_controller_spec.rb ./spec/controllers/subscriptions_controller_spec.rb ./spec/decorators/email_decorator_spec.rb ./spec/decorators/output_metrics_decorator_spec.rb ./spec/decorators/subscription_decorator_spec.rb ./spec/external/admin/coupons_spec.rb ./spec/external/subscriptions_spec.rb ./spec/jobs/delete_draft_emails_spec.rb ./spec/jobs/send_draft_emails_spec.rb ./spec/jobs/send_email_spec.rb ./spec/lib/events/cache_spec.rb ./spec/lib/events/client_spec.rb ./spec/lib/events/customer_spec.rb ./spec/lib/events/event_spec.rb ./spec/lib/events/session_spec.rb ./spec/mailers/trigger_mailer_spec.rb ./spec/models/anonymous_user_spec.rb ./spec/models/coupon_spec.rb ./spec/models/email_layout_spec.rb ./spec/models/email_spec.rb ./spec/models/email_template_spec.rb ./spec/models/output_extensions/conversions_spec.rb ./spec/models/output_extensions/send_emails_spec.rb ./spec/models/output_spec.rb ./spec/models/segment_spec.rb ./spec/models/sender_identity_spec.rb ./spec/models/subscription_spec.rb ./spec/models/trigger_extensions/map_reduce_spec.rb ./spec/models/trigger_extensions/match_spec.rb ./spec/models/trigger_spec.rb ./spec/models/trigger_template/blank_spec.rb ./spec/models/trigger_template/free_to_paid_spec.rb ./spec/models/trigger_template/inactivity_spec.rb ./spec/models/trigger_template/signup_spec.rb ./spec/models/trigger_template_spec.rb ./spec/models/user_spec.rb ./spec/presenters/output_metrics/mysql_store_spec.rb ./spec/presenters/output_metrics/redis_store_spec.rb ./spec/presenters/output_metrics_spec.rb ./spec/presenters/trigger_metrics_spec.rb failed

Tasks: TOP => spec
(See full trace by running task with --trace)