Process completed with exit code 1.

SyncDecidedAppealsHelper #sync_decided_appeals Job syncs decided appeals decision_mailed status Failure/Error: DatabaseCleaner[:active_record, { db: :primary }].clean ActiveRecord::ConnectionNotEstablished: connection is closed

SyncDecidedAppealsHelper #sync_decided_appeals catches standard errors

Process completed with exit code 1.

Tasks related to an existing Appeal - In Correspondence Details Page user waives evidence submission window task on an appeal completes the evidence submission window task Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

Test::CorrespondenceController private methods #connect_corr_with_vet creates correspondences and associated documents for each valid file number Failure/Error: if !unassigned_review_package_tasks.count.positive? ActiveRecord::EagerLoadPolymorphicError: Cannot eagerly load the polymorphic association :correspondence

Test::CorrespondenceController private methods #connect_corr_with_vet assigns NOD document types correctly Failure/Error: if !unassigned_review_package_tasks.count.positive? ActiveRecord::EagerLoadPolymorphicError: Cannot eagerly load the polymorphic association :correspondence

Test::CorrespondenceController private methods #connect_corr_with_vet creates a BatchAutoAssignmentAttempt and enqueues AutoAssignCorrespondenceJob Failure/Error: if !unassigned_review_package_tasks.count.positive? ActiveRecord::EagerLoadPolymorphicError: Cannot eagerly load the polymorphic association :correspondence

Process completed with exit code 1.

Task Links on Your Correspondence and Correspondence Cases pages When a user clicks a task link in veterans details column the task is an active CorrespondenceIntakeTask routes to the Correspondence Intake page Failure/Error: expect(page).to have_content("Add Related Correspondence") expected to find text "Add Related Correspondence" in "CaseflowQueue\nSearch cases\nCSSID0385371 (VACO)\nYour Correspondence\nSwitch views\nAssignedIn ProgressCompleted\nCorrespondence assigned to you:\nFilter table by any of its columns\nViewing 1-2 of 2 total\nVeteran Details\nPackage Document Type\nVA DOR\nDays Waiting\nNotes\nBob Smithwillms (980032623) Non-NOD 10/23/2024 0\nBob Smithwillms (980032623) Non-NOD 10/23/2024 0\nViewing 1-2 of 2 total\nSend feedback"

Process completed with exit code 1.

Attorney checkout flow given a valid ama appeal submits draft decision Failure/Error: expect(page).to have_content(COPY::JUDGE_CHECKOUT_DISPATCH_SUCCESS_MESSAGE_TITLE % appeal.veteran_full_name) expected to find text "Thank you for reviewing Bob Smithhansen's decision." in "CaseflowQueue\nSearch cases\nCSSID0142053 (VACO)\nBob SmithhansenVeteran ID: 980010012 \nView all cases\nEvaluate Decision\nCurrently active tasks\nASSIGNED ON\n10/24/2024\nDAYS WAITING\n0\nGray dot: Pending\nASSIGNED TO\nCSSID0142053\nASSIGNED BY\nL. Roth\nTASK\nReview\nView task instructions\nCase Timeliness\nCase Type: Original\nTotal days since attorney assigned: 0\nDays worked by attorney: 0\n\n10/24/24 - Assigned to attorney\nNo tasks to show\n10/24/24 - Decision submitted to judge\n\nComplexity of case\nHow would you rate the complexity of this case?\nEasy\nMedium\nHard\nQuality of work\nHow would you rate the overall quality of this case?\n5 - Outstanding\n4 - Exceeds expectations\n3 - Meets expectations\n2 - Needs improvements\n1 - Does not meet expectations\nIdentify positive feedback:\nResponsive to contentions and theories\nWell-analyzed lay evidence\nWell-analyzed medical evidence\nGood hidden issue-spotting and analysis\nConcise, understandable, Veteran-centric writing\nAppropriate use of law, precedential opinion and administrative procedure\nLogically organized\nNo substantive revisions\nWell proofed (no to minimal typos/grammar errors)\nWell-annotated file for VLJ review to include appropriate use of tags and comments\nRemand is concise and provides detailed, understandable directives\nIdentify areas for improvement\nThe attorney did not properly consider and apply:\nTheory contention\nCase law\nStatute/regulation\nAdministrative procedure, procedure opinion\nRelevant records (medical, service, employment)\nLay evidence\nOther areas for improvement:\nDid not properly identify and address one or more issues before the Board\nFindings are not supported by adequate reasons, bases\nDid not adequately address due process violations\nRemands not complete, legally sufficient or require necessary development\nMajor or frequent spelling, grammar, typographical, usage, formatting errors\nAdditional Comments\nOptional\nShare more details about your evaluation\nShare more details about your evaluation\nCancelBack\nContinue\nSend feedback"

Process completed with exit code 1.

CorrespondenceAutoAssigner#perform when a run is permitted with unassigned ReviewPackageTasks when assignable users exist assigns review package tasks to assignable users Failure/Error: if !unassigned_review_package_tasks.count.positive? ActiveRecord::EagerLoadPolymorphicError: Cannot eagerly load the polymorphic association :correspondence

CorrespondenceAutoAssigner#perform when a run is permitted with unassigned ReviewPackageTasks when assignable users exist with varying va_date_of_receipt values assigns the correspondence with the oldest va_date_of_receipt first Failure/Error: if !unassigned_review_package_tasks.count.positive? ActiveRecord::EagerLoadPolymorphicError: Cannot eagerly load the polymorphic association :correspondence

CorrespondenceAutoAssigner#perform when a run is permitted with unassigned ReviewPackageTasks when assignable users do NOT exist updates the BatchAutoAssignmentAttempt with a capacity error message Failure/Error: if !unassigned_review_package_tasks.count.positive? ActiveRecord::EagerLoadPolymorphicError: Cannot eagerly load the polymorphic association :correspondence

CorrespondenceAutoAssigner#perform when a run is permitted when unassigned ReviewPackageTasks do NOT exist updates the BatchAutoAssignmentAttempt with a no correspondences error message Failure/Error: if !unassigned_review_package_tasks.count.positive? ActiveRecord::EagerLoadPolymorphicError: Cannot eagerly load the polymorphic association :correspondence

Process completed with exit code 1.

The Correspondence Details All Tasks Actions testing tasks actions for Other motion tasks checks that Other motion task can be cancelled. Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

The Correspondence Details All Tasks Actions testing tasks actions for Other motion tasks checks that Other motion task can be completed. Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

The Correspondence Details All Tasks Actions testing tasks actions for Other motion tasks Verify Other motion task with Assign to team action dropdown Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

The Correspondence Details All Tasks Actions testing tasks actions for Other motion tasks Verify Other motion task with Change task type action dropdown Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

The Correspondence Details All Tasks Actions testing tasks actions for FOIA request tasks checks that FOIA request task can be cancelled. Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

The Correspondence Details All Tasks Actions testing tasks actions for FOIA request tasks checks that FOIA request task can be completed. Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

The Correspondence Details All Tasks Actions testing tasks actions for FOIA request tasks Verify FOIA request task with Assign to team action dropdown Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

The Correspondence Details All Tasks Actions testing tasks actions for FOIA request tasks Verify FOIA request task with Change task type action dropdown Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

The Correspondence Details All Tasks Actions testing tasks actions for CAVC Correspondence tasks checks that CAVC Correspondence task can be cancelled. Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

The Correspondence Details All Tasks Actions testing tasks actions for CAVC Correspondence tasks checks that CAVC Correspondence task can be completed. Failure/Error: container.find(selector, **keyword_args) Capybara::ElementNotFound: Unable to find css ".cf-select__control"

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/

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

Attorney checkout flow AC 1.5 It passes the feature tests for adding a new issue appeal PACT Adding a new issue with PACT Skipped: No reason given

Attorney checkout flow AC 1.6 It passes the feature tests for adding a new issue appeal MST & PACT Adding a new issue with MST & PACT Skipped: No reason given

Persistence of the intake correspondence page step 1 creates a correspondence_intake record on page load Skipped: Temporarily skipped with xit

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

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/

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

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

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

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/

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

Correspondence Details Response Letters Module Verifying Correspondence Details Response Letters page Verify the Add button for Response Letters in details page Skipped: Temporarily skipped with xit

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/

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

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/

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

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

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

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.

Hearing Schedule Daily Docket for RO ViewHearSched User cannot view docket notes 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/

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/

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

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 process '/usr/bin/git' failed with exit code 128