Fixing flaky test - APPEALS-57724 #23904
Annotations
9 warnings
|
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/queue/case_details_spec.rb#L680
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/feature/queue/case_details_spec.rb#L709
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/feature/queue/mail_task_spec.rb#L283
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/feature/queue/mail_task_spec.rb#L283
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/feature/queue/mail_task_spec.rb#L283
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
|
|
RSpec via knapsack_pro Queue Mode:
spec/feature/queue/mail_task_spec.rb#L283
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
|
|
Post Run actions/checkout@v3
The process '/usr/bin/git' failed with exit code 128
|
|
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