Closed xdxxxdx closed 6 months ago
Hi, there is indeed something wrong with the gtfs2ldes image. I noticed this too. Julian has made some fixes on December 20th but unfortunately these introduced a different issue. I made him aware of that.
As the gtfs2ldes-js image is not under our control I have disabled tests 007 and 013 until a fix is available here.
It turned out to be our mistake: due to the multi-typed server change we could not determine the actual member if multiple named nodes were in the ingested member message. This is now fixed by using the isVersionOf to determine the member id.
GitHub action result: https://github.com/xdxxxdx/VSDS-LDES-E2E-testing/actions/runs/6967548568/job/18961230745
With tags for Sprint 39: VSDS-LDESServer4J
VSDS-Linked-Data-Interactions
ldi-workbench-nifi tag: ldes/ldi-workbench-nifi:1.10.0-SNAPSHOT
ldi-orchestrator tag: ldes/ldi-orchestrator:1.10.0-SNAPSHOT
The 3 failing actions are due to the default configuration of gtfs2ldes-js![image](https://github.com/Informatievlaanderen/VSDS-LDES-E2E-testing/assets/15314807/9ee7db2b-b200-422b-9875-0f327a44db4b)
https://github.com/Informatievlaanderen/VSDS-LDES-E2E-testing/blob/main/tests/007.server-ingest-large-ldes/docker-compose.yml
GTFS_SOURCE:-https://www.rtd-denver.com/files/gtfs/bustang-co-us.zip etc..
Logs: