Bigtests consistently failing with "Calendar settings settings should have proper amount of links"

Description

See https://jenkins-aws.indexdata.com/blue/organizations/jenkins/folio-org%2Fui-calendar/detail/PR-259/2/tests for an example. I am just merging locale files, so that should have no effect on whether tests pass or not.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Khalilah Gambrell April 22, 2020 at 12:15 PM

, per "I get the same result when I run the tests locally. It’s possible some stripes-components internals has changed and ui-calendar has a test with a local selector that doesn’t grok that. But the precis: the failure looks legit to me."

Maxim Didenko April 22, 2020 at 6:57 AM

I will take a look, maybe we have a problem in this module.

Peter Murray April 21, 2020 at 6:56 PM
Edited

I'm running a batch job now (https://github.com/folio-org/ui-calendar/pull/261) and the error at the bottom of your console is the same as I'm seeing at the bottom of mine (https://jenkins-aws.indexdata.com/job/folio-org/job/ui-calendar/job/PR-261/2/):
{{
SUMMARY:
✔ 217 tests completed
✖ 1 test failed

FAILED TESTS:
Calendar settings
settings
✖ should have proper amount of links
Chrome 81.0.4044 (Linux 0.0.0)
AssertionError: expected 2 to equal 1
}}

Maxim Didenko April 21, 2020 at 6:39 PM

I can't open logs for your PR, but I have triggered build for master branch and received following error - https://jenkins-aws.indexdata.com/job/folio-org/job/ui-calendar/job/master/58/console Is it the same error you had in your PR?

Peter Murray April 21, 2020 at 6:11 PM

Does this affect other modules? I ask because this is the only module that fails consistently despite repeated restarts of the CI tests. (This pull request failed 6 times before I gave up; there hasn't been a successful test run since March 16.)

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Vega

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created April 16, 2020 at 10:43 PM
Updated June 10, 2020 at 3:42 PM
Resolved April 29, 2020 at 2:50 PM
TestRail: Cases
TestRail: Runs