You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the record: I got "Failed to parse benchmark configuration" errors and it took some time to figure out why.
/home/ubuntu/git/ldbc-graphalytics-platform-graphblas/graphalytics-1.0.0-graphblas-0.1-SNAPSHOT/bin/sh/../..//config/:/home/ubuntu/git/ldbc-graphalytics-platform-graphblas/graphalytics-1.0.0-graphblas-0.1-SNAPSHOT/bin/sh/../..//lib/graphalytics-platforms-graphblas-0.1-SNAPSHOT-default.jar:
11:22 [INFO ] Initializing Benchmark Suite.
11:22 [INFO ] Loading Benchmark...
Exception in thread "main" science.atlarge.graphalytics.configuration.GraphalyticsLoaderException: Failed to parse benchmark configuration.
at science.atlarge.graphalytics.BenchmarkSuite.main(BenchmarkSuite.java:75)
Caused by: science.atlarge.graphalytics.configuration.InvalidConfigurationException: Cannot retrieve properties from file: benchmark.properties
at science.atlarge.graphalytics.configuration.ConfigurationUtil.loadConfiguration(ConfigurationUtil.java:48)
at science.atlarge.graphalytics.execution.BenchmarkLoader.<init>(BenchmarkLoader.java:76)
at science.atlarge.graphalytics.BenchmarkSuite.main(BenchmarkSuite.java:71)
The cause was that I created a config directory in the root of the repository. This prevented the packaging script (mvn package) to add some other configuration files such as graphs.properties, granula.properties, etc. The solution is simply not to create this directory in the repository root.
For the record: I got "Failed to parse benchmark configuration" errors and it took some time to figure out why.
The cause was that I created a
config
directory in the root of the repository. This prevented the packaging script (mvn package
) to add some other configuration files such asgraphs.properties
,granula.properties
, etc. The solution is simply not to create this directory in the repository root.See also #145.
The text was updated successfully, but these errors were encountered: