Open ShanaLMoore opened 1 year ago
My time box for this has expired. I will go to Rob's office hrs for help.
look into selenium retry gem
ssh into pipeline and re run the seed #
consider using: https://github.com/NoRedInk/rspec-retry
Low priority and not urgent so putting this back in the backlog for now since rerunning the pipeline usually resolves this. we'd rather save our billable hrs for actual bug tickets and client priorities.
Client is OK to abandon selenium if there is another tool that's more reliable.
ref: https://github.com/WGBH-MLA/ams/actions/runs/5872454591/job/15924647625?pr=755
our rails 6 pipeline is full of selenium errors that prevent the spec from actually running. retriggering it often succeeds, it just sucks and is inconvenient to have to do that several times:
LaRita has also been seeing this issue occasionally occur when running specs locally.