-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FVTs fail when run with local graph repository #7624
Comments
This was done with HEAD 67cf556 (ie before any issues that broke CTS as in the referenced issue), and may indicate problems with graph repository FVTs more generally |
Similar failures occur with
which suggests this is a longer/different issue to the latest issues seen with CTS Suggestion:
These are tactical. A long term solution would still be to
|
The fix for #7618 also fixes running FVTs against the graph repo (at least on main). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions. |
FVTs currently fail using the local graph repository
Egeria's FVT tests currently run with 'inmemory' repository only. This is due to
In the past, we did run both local graph & inmem
To debug #7618 I tried running FVTs against graph, rather than inmemory. this was done by search/replace of 'inmemory-repository' with local-graph-repository.
Having done this many tests fail.
For a specific example I modified asset consumer fvt:
Prior to this change FVT passed successfully. After, some tests fail
The text was updated successfully, but these errors were encountered: