Skip to content

move setting to around blocks #939

move setting to around blocks

move setting to around blocks #939

Triggered via push June 5, 2024 13:38
Status Failure
Total duration 4m 6s
Artifacts

tests.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 13 warnings
Tests: spec/system/search/user_search_spec.rb#L49
user search role search in admin mode context Failure/Error: @_setting = create(:setting, mission: nil) ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_settings_on_mission_id_IS_NULL" DETAIL: Key ((mission_id IS NULL))=(t) already exists.
Tests: spec/system/search/user_search_spec.rb#L22
user search search in mission context Failure/Error: @_setting = create(:setting, mission: nil) ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_settings_on_mission_id_IS_NULL" DETAIL: Key ((mission_id IS NULL))=(t) already exists.
Tests: spec/models/ability/question_ability_spec.rb#L11
abilities for questions for coordinator role should be able to create and index Failure/Error: @_setting = create(:setting, mission: nil) ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_settings_on_mission_id_IS_NULL" DETAIL: Key ((mission_id IS NULL))=(t) already exists.
Tests: spec/models/ability/question_ability_spec.rb#L52
abilities for questions for coordinator role when std copy should be able to do all except update_code Failure/Error: @_setting = create(:setting, mission: nil) ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_settings_on_mission_id_IS_NULL" DETAIL: Key ((mission_id IS NULL))=(t) already exists.
Tests: spec/models/ability/question_ability_spec.rb#L41
abilities for questions for coordinator role when live should be able show and update only Failure/Error: @_setting = create(:setting, mission: nil) ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_settings_on_mission_id_IS_NULL" DETAIL: Key ((mission_id IS NULL))=(t) already exists.
Tests: spec/models/ability/question_ability_spec.rb#L19
abilities for questions for coordinator role when draft should be able to do all Failure/Error: @_setting = create(:setting, mission: nil) ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_settings_on_mission_id_IS_NULL" DETAIL: Key ((mission_id IS NULL))=(t) already exists.
Tests: spec/models/ability/question_ability_spec.rb#L30
abilities for questions for coordinator role when draft with answers should be able to do all but destroy and update core Failure/Error: @_setting = create(:setting, mission: nil) ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_settings_on_mission_id_IS_NULL" DETAIL: Key ((mission_id IS NULL))=(t) already exists.
Tests: spec/models/replication/question_replication_spec.rb#L59
Question to_mission code sync when new code conflicts with existing question in mission should sync Failure/Error: @_setting = create(:setting, mission: nil) ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_settings_on_mission_id_IS_NULL" DETAIL: Key ((mission_id IS NULL))=(t) already exists.
Tests: spec/models/replication/question_replication_spec.rb#L47
Question to_mission code sync when no conflicts should sync Failure/Error: @_setting = create(:setting, mission: nil) ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_settings_on_mission_id_IS_NULL" DETAIL: Key ((mission_id IS NULL))=(t) already exists.
Tests: spec/models/replication/question_replication_spec.rb#L25
Question to_mission basic should not change code or name Failure/Error: @_setting = create(:setting, mission: nil) ActiveRecord::RecordNotUnique: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_settings_on_mission_id_IS_NULL" DETAIL: Key ((mission_id IS NULL))=(t) already exists.
Tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2, actions/setup-node@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests: app/javascript/components/Filters/model.js#L133
Unexpected console statement
Tests: app/javascript/packs/enketo.js#L43
Unexpected console statement
Tests: app/javascript/packs/enketo.js#L57
Unexpected alert
Tests: app/javascript/packs/enketo.js#L80
Unexpected console statement
Tests: app/javascript/packs/enketo.js#L91
Unexpected alert
Tests: app/javascript/packs/enketo.js#L94
Unexpected console statement
Tests: spec/models/broadcaster_spec.rb#L16
Sms::Broadcaster with adapter set in mission settings builds appropriate adapter and Sms::Broadcast instance Skipped: Temporarily skipped with xit
Tests
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/