jena: Intermittent e2e/cypress test failure.

This issue is to collect information

This test in Fuseki UI has started failing for me again.

It has been an intermittent failure; typically if a codebase works (mavne build passes) it keeps working and if it fails it fails nearly every build.

[INFO] [TESTS]   ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
[INFO] [TESTS]   │ ✖  datasets.cy.js                           00:27        9        8        1        -        - │
[INFO] [TESTS]   ├────────────────────────────────────────────────────────────────────────────────────────────────┤
[INFO] [TESTS]   │ ✔  query.cy.js                              00:01        1        1        -        -        - │
[INFO] [TESTS]   └────────────────────────────────────────────────────────────────────────────────────────────────┘
[INFO] [TESTS]     ✖  1 of 2 failed (50%)                      00:28       10        9        1        -        -

It is not maven dependency - running it outside maven has the same failure mode.

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 15 (15 by maintainers)

Commits related to this issue

GH-1644: Log test failure but not fail whole build — committed to apache/jena by afs 2 years ago
GH-1644: Add start-server-and-test, remove concurrently, and simplify packages.json scripts. Add docs. — committed to kinow/jena by kinow a year ago
GH-1644: Add start-server-and-test, remove concurrently, and simplify packages.json scripts. Add docs. — committed to kinow/jena by kinow a year ago
GH-1644: Add start-server-and-test, remove concurrently, and simplify packages.json scripts. Add docs. — committed to apache/jena by kinow a year ago

Most upvoted comments

🎆 🍾

afs on Jan 31, 2023

(updating status)

Following on from #1718.

If errors occur, I’ve only seen this 3-1 pattern, whereas it was 1-0.

[INFO] [TESTS]   ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
[INFO] [TESTS]   │ ✖  datasets.cy.js                           00:30        9        -        3        -        6 │
[INFO] [TESTS]   ├────────────────────────────────────────────────────────────────────────────────────────────────┤
[INFO] [TESTS]   │ ✖  query.cy.js                              00:15        2        -        1        -        1 │
[INFO] [TESTS]   └────────────────────────────────────────────────────────────────────────────────────────────────┘
[INFO] [TESTS]     ✖  2 of 2 failed (100%)                     00:45       11        -        4        -        7  
[INFO] [TESTS]

afs on Jan 25, 2023

Currently, the e2e tests are set to not fail the build should an error occur.

afs on Jan 7, 2023

The 3 test failure in #1480 was because HOST was set which it isn’t now.

We should probably undo 242725c8 which reorders tests which seemed to work at the time.

If necessary, we can turn off the e2e test for the release when built on my machine. We can be fairly sure the tests do what they should do and it is an environment or framework issue.

afs on Dec 27, 2022

Linux. Docker Desktop installed.

I now have the situation where if it is failing then stopping docker.service causes the build to work again. Restarting usually (not always!) causes the build to fail again.

Docker reconfigures local networking.

afs on Nov 30, 2022