feature/APPEALS-32376: Re-architect How Caseflow Stores and Processes Hearing Times #19823
Annotations
14 warnings
|
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/
|
|
Post Run actions/checkout@v3
The process '/usr/bin/git' failed with exit code 128
|
|
capybara-artifacts
No files were found with the provided path: ./tmp/capybara. No artifacts will be uploaded.
|
|
RSpec via knapsack_pro Queue Mode:
spec/feature/hearings/daily_docket/ro_viewhearsched_spec.rb#L8
Hearing Schedule Daily Docket for RO ViewHearSched User cannot view docket notes
Skipped: Flaky test
|
|
RSpec via knapsack_pro Queue Mode:
spec/support/shared_examples/requests/api/v3/issues/ama/shared_examples_request_issues_spec.rb#L189
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/support/shared_examples/requests/api/v3/issues/ama/shared_examples_request_issues_spec.rb#L202
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/support/shared_examples/requests/api/v3/issues/ama/shared_examples_request_issues_spec.rb#L242
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/support/shared_examples/requests/api/v3/issues/ama/shared_examples_request_issues_spec.rb#L301
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/support/shared_examples/requests/api/v3/issues/ama/shared_examples_request_issues_spec.rb#L281
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/support/shared_examples/requests/api/v3/issues/ama/shared_examples_request_issues_spec.rb#L261
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/support/shared_examples/requests/api/v3/issues/ama/shared_examples_request_issues_spec.rb#L169
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/support/shared_examples/requests/api/v3/issues/ama/shared_examples_request_issues_spec.rb#L130
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/support/shared_examples/requests/api/v3/issues/ama/shared_examples_request_issues_spec.rb#L150
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 artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "artifact".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Loading