Nigel Jones

Also user has indicated 'It happens on org.odpi.egeria:design-model-client:jar:3.5-SNAPSHOT' so this may be another area where the build fails with additional test flags

As we are moving to gradle, I propose we do not fix this

Is there a reason not to use the existing strategy? Is it to ease migration over to the view services since the ui-server-chassis is the existing endpoint for the business...

Tried so far - Disable caching in gradle properties - Disable git action configured caching - alternative jvms Observed - existing environments don't seem to hit this issue (even if...

Also now occuring on data manager: ``` > Task :open-metadata-test:open-metadata-fvt:access-services-fvt:data-engine-fvt:test FindFVT > find(String, DataEngineClient, RepositoryService) > org.odpi.openmetadata.accessservices.dataengine.fvt.FindFVT.find(String, DataEngineClient, RepositoryService)[2] FAILED org.odpi.openmetadata.frameworks.connectors.ffdc.InvalidParameterException at FindFVT.java:42 > Task :open-metadata-test:open-metadata-fvt:access-services-fvt:data-manager-fvt:test FAILED DataManagerOMASIT > testCreateEvents(String)...

Running more tests in parallel it seems as if every FVT may now be failing with guid search issues. EVERY test most likely. May just be seen as I upgraded...

Noting configuration on failing system: ``` jonesn@ubuntu-buildtest:~/src/egeria$ java -version openjdk version "11.0.13" 2021-10-19 OpenJDK Runtime Environment Temurin-11.0.13+8 (build 11.0.13+8) OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (build 11.0.13+8, mixed mode) jonesn@ubuntu-buildtest:~/src/egeria$ cat...

Tips on debugging the graph. * Follow tutorial for installing janusgraph using https://jointhegraph.github.io/articles/installing-janusgraph-and-its-storage-backends/installing-janusgraph-and-testing-it-with-the-inmemory-storage-backend/ -- but note, download the latest version ie 0.6.0 * See https://jointhegraph.github.io/articles/installing-janusgraph-and-its-storage-backends/configuring-janusgraph-to-use-oracle-berkeley-db/ to switch configuration to berkely...

A query on the graph (for the analytics modeling FVT) seems to show iBASEMODULE is present within the underlying graph -> https://gist.github.com/443b5f9c1f14b40ce007814b6399c9f0

Possible fix merged. Will summarise after