Process completed with exit code 1.

Process completed with exit code 1.

Hearings::TranscriptionWorkOrderController GET #display_wo_contents when work order contents are found returns a success response Failure/Error: wo_content = ::TranscriptionWorkOrder.display_wo_contents(@task_number) #<TranscriptionWorkOrder (class)> received :display_wo_contents with unexpected arguments expected: ("TASK123") got: (nil) Diff: @@ -1,2 +1,2 @@ -["TASK123"] +[nil] Please stub a default value first if message might be received with other args as well.

Hearings::TranscriptionWorkOrderController GET #display_wo_contents when work order contents are found returns the work order contents in JSON Failure/Error: wo_content = ::TranscriptionWorkOrder.display_wo_contents(@task_number) #<TranscriptionWorkOrder (class)> received :display_wo_contents with unexpected arguments expected: ("TASK123") got: (nil) Diff: @@ -1,2 +1,2 @@ -["TASK123"] +[nil] Please stub a default value first if message might be received with other args as well.

Hearings::TranscriptionWorkOrderController GET #display_wo_contents when work order contents are not found returns a not found response Failure/Error: wo_content = ::TranscriptionWorkOrder.display_wo_contents(@task_number) #<TranscriptionWorkOrder (class)> received :display_wo_contents with unexpected arguments expected: ("TASK123") got: (nil) Diff: @@ -1,2 +1,2 @@ -["TASK123"] +[nil] Please stub a default value first if message might be received with other args as well.

Hearings::TranscriptionWorkOrderController GET #display_wo_contents when work order contents are not found returns an error message in JSON Failure/Error: wo_content = ::TranscriptionWorkOrder.display_wo_contents(@task_number) #<TranscriptionWorkOrder (class)> received :display_wo_contents with unexpected arguments expected: ("TASK123") got: (nil) Diff: @@ -1,2 +1,2 @@ -["TASK123"] +[nil] Please stub a default value first if message might be received with other args as well.

Hearings::TranscriptionWorkOrderController POST #unassign_wo when unassigning work order is successful returns a success response Failure/Error: wo_content = ::TranscriptionWorkOrder.unassign_wo(@task_number) #<TranscriptionWorkOrder (class)> received :unassign_wo with unexpected arguments expected: ("TASK123") got: (nil) Diff: @@ -1,2 +1,2 @@ -["TASK123"] +[nil] Please stub a default value first if message might be received with other args as well.

Hearings::TranscriptionWorkOrderController POST #unassign_wo when unassigning work order is successful returns the banner messages in JSON Failure/Error: wo_content = ::TranscriptionWorkOrder.unassign_wo(@task_number) #<TranscriptionWorkOrder (class)> received :unassign_wo with unexpected arguments expected: ("TASK123") got: (nil) Diff: @@ -1,2 +1,2 @@ -["TASK123"] +[nil] Please stub a default value first if message might be received with other args as well.

Hearings::TranscriptionWorkOrderController POST #unassign_wo when unassigning work order fails returns an internal server error response Failure/Error: wo_content = ::TranscriptionWorkOrder.unassign_wo(@task_number) #<TranscriptionWorkOrder (class)> received :unassign_wo with unexpected arguments expected: ("TASK123") got: (nil) Diff: @@ -1,2 +1,2 @@ -["TASK123"] +[nil] Please stub a default value first if message might be received with other args as well.

Hearings::TranscriptionWorkOrderController POST #unassign_wo when unassigning work order fails returns an error message in JSON Failure/Error: wo_content = ::TranscriptionWorkOrder.unassign_wo(@task_number) #<TranscriptionWorkOrder (class)> received :unassign_wo with unexpected arguments expected: ("TASK123") got: (nil) Diff: @@ -1,2 +1,2 @@ -["TASK123"] +[nil] Please stub a default value first if message might be received with other args as well.

Hearings::TranscriptionWorkOrderController POST #unassigning_work_order when unassigning work order is successful returns a success response Failure/Error: Transcription.unassign_by_task_number(@task_number) #<Transcription(id: integer, created_at: datetime, created_by_id: integer, deleted_at: datetime, expected_return_date: date, hearing_id: integer, hearing_type: string, problem_notice_sent_date: date, problem_type: string, requested_remedy: string, return_date: date, sent_to_transcriber_date: date, task_id: integer, task_number: string, transcriber: string, transcription_contractor_id: integer, transcription_status: string, updated_at: datetime, updated_by_id: integer, uploaded_to_vbms_date: date) (class)> received :unassign_by_task_number with unexpected arguments expected: ("TASK123") got: (nil) Diff: @@ -1,2 +1,2 @@ -["TASK123"] +[nil] Please stub a default value first if message might be received with other args as well.

Process completed with exit code 1.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

api/v2/appeals /api/v2/appeals get successful returns a 200 response Skipped: No reason given

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.

The process '/usr/bin/git' failed with exit code 128

Metrics::V2::LogsController pdf_page_render_time_in_ms Feature toggle enabled create a metric for pdf_page_render_time_in_ms Skipped: Temporarily disabled with xscenario

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues behaves like it_should_respond_with_legacy_present should respond with legacy_appeals_present Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues behaves like it_should_respond_with_associated_request_issues should respond with the associated request issues Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues behaves like it_should_respond_with_same_multiple_decision_issues_per_request_issue should respond with the same multiple decision issues per request issue Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_number_of_paginated_issues should only show number of request issues listed in the paginates_per value on first page Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_remaining_issues should only show remaining request issues on next page Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_page_1_when_page_0 should show page 1 when attempting to get page 0 Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_default_to_page_1 should default to page 1 Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_first_page_if_page_negatvie should show the first page if page is negative Skipped: Flakey test

Api::V3::Issues::Ama::VeteransController#show when feature is enabled when a veteran is found when there is no error when a veteran has a legacy appeal when a veteran has multiple decision issues with multiple request issues when number of request issues exceeds paginates_per value behaves like it_should_show_last_page_if_page_larger_than_total should show last page if page larger than total Skipped: Flakey test

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Hearing Schedule Daily Docket for RO ViewHearSched User cannot view docket notes Skipped: Flaky test

IntakeStartValidator#validate when BGS shows a station conflict sets error_code "veteran_not_modifiable" when BGS shows a station conflict Skipped: Flaky test

IntakeStartValidator#validate when BGS shows a station conflict for an Appeal intake user is on the BVA Intake team sets a veteran_not_modifiable error code Skipped: Flaky test

No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.

The process '/usr/bin/git' failed with exit code 128

Case details attorney case details view veteran records have been merged and Veteran has multiple active phone numbers in SHARE access the appeal's case details Skipped: This test fails in GHA but not locally

Case details when an appeal has some number of documents with reader role reader link appears on page and sends us to reader Skipped: Flaky test

MailTasks Hearing Postponement Request Mail Task mark as complete ruling is granted schedule immediately AMA appeal unscheduled hearing sends proper notifications Skipped: test is failing in local env and github actions

MailTasks Hearing Postponement Request Mail Task mark as complete ruling is granted schedule immediately AMA appeal scheduled hearing sends proper notifications Skipped: test is failing in local env and github actions

MailTasks Hearing Postponement Request Mail Task mark as complete ruling is granted schedule immediately Legacy appeal unscheduled hearing sends proper notifications Skipped: test is failing in local env and github actions

MailTasks Hearing Postponement Request Mail Task mark as complete ruling is granted schedule immediately Legacy appeal scheduled hearing sends proper notifications Skipped: test is failing in local env and github actions

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.

The process '/usr/bin/git' failed with exit code 128

Postpone hearing with schedule direct to video/virtual feature disabled for AMA appeals when rescheduling Skipped: This functionality is no longer in use.

Postpone hearing with schedule direct to video/virtual feature disabled for AMA appeals behaves like an AMA appeal and schedule later with admin action Skipped: This functionality is no longer in use.

Postpone hearing with schedule direct to video/virtual feature disabled for AMA appeals behaves like an AMA appeal and schedule later Skipped: This functionality is no longer in use.

Postpone hearing with schedule direct to video/virtual feature disabled for AMA appeals behaves like an AMA appeal then change to held Skipped: This functionality is no longer in use.

Postpone hearing with schedule direct to video/virtual feature disabled for a Legacy appeal when rescheduling on the same day Skipped: This functionality is no longer in use.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.

NonComp Reviews Queue with an existing organization filtering reviews by appeal type Skipped: No reason given

NonComp Reviews Queue with an existing organization filtering reviews by issue type Skipped: No reason given

NonComp Reviews Queue Issue Type filtering and sorting edge cases The Issue type column should orderable and filterable at the same time Skipped: No reason given

BgsShareErrorFixJob BGS::ShareError RIU when EPE has established_at date clears the BGS::ShareError on the RIU Skipped: flaky test

BgsShareErrorFixJob BGS::ShareError RIU when EPE does not have established_at date does not clear the BGS::ShareError on the RIU Skipped: flaky test

BgsShareErrorFixJob BGS::ShareError RIU when the RIU does not have the BGS::ShareError does not attempt to clear the error Skipped: flaky test

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

ClaimHistoryService.build_events with filters days waiting filter equal to number of days should only return events for tasks that match the days waiting filter Skipped: Flakey test

BgsPowerOfAttorney record expirations by_file_number record is expired Skipped: Test is flaky

BgsPowerOfAttorney record expirations by_file_number record is not expired Skipped: Test is flaky

BgsPowerOfAttorney.find_or_create_by_claimant_participant_id when concurrent calls cause a race condition does not raise an error on unique constraint violation Skipped: Test is flaky

BgsPowerOfAttorney.find_or_create_by_file_number when concurrent calls cause a race condition does not raise an error on unique constraint violation Skipped: Test is flaky

No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.

Establish Claim - ARC Dispatch As a caseworker For a full grant When there is an existing 070 EP Assigning it to complete the claims establishment Skipped: Test is hanging in GHA

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.

FetchAllActiveLegacyAppealsJob#find_and_create_appeal_state_for_active_legacy_appeals when there are both OPEN & CLOSED Legacy Appeals in the database only OPEN Legacy Appeal records will be added to the Appeal States table Skipped: Flaky test

The process '/usr/bin/git' failed with exit code 128

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache/restore@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The process '/usr/bin/git' failed with exit code 128