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

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.

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