Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: None
Affects Version/s: 8.15.0.Final
Component/s: optaplanner-benchmark, optaplanner-quarkus
Labels:
None

Sprint:
2022 Week 02-04 (from Jan 10)
Steps to Reproduce:

Hide

Remove this line and rerun:
https://github.com/ge0ffrey/dimacs-vrp-challenge-2021/blob/main/cvrp-benchmark/src/main/resources/application.properties#L3

Show
Remove this line and rerun: https://github.com/ge0ffrey/dimacs-vrp-challenge-2021/blob/main/cvrp-benchmark/src/main/resources/application.properties#L3
Docs QE Status:
NEW
QE Status:
NEW

Description

Even if I provide a full-fledged solverBenchmarkConfig.xml, OptaPlanner Benchmark still requires at least one property to be specified in application.properties.

This is confusing and leads to situations where the config is split between the properties and the XML.

When the property is removed, I get:

2022-01-10 08:30:27,046 ERROR [io.qua.run.Application] (Quarkus Main Thread) Failed to start application (with profile dev): java.lang.IllegalStateException: At least one of the properties quarkus.optaplanner.benchmark.solver.termination.spent-limit, quarkus.optaplanner.benchmark.solver.termination.best-score-limit, quarkus.optaplanner.benchmark.solver.termination.unimproved-spent-limit is required if the inherited solver config does not have termination configured.

This happens even when I actually have the <inheritedSolverBenchmark /> configured.

Attachments

Activity

People

Assignee:: Christopher Chianelli

Reporter:: Lukáš Petrovický (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2022/01/10 7:29 AM

Updated:: 2022/01/11 1:58 PM

Resolved:: 2022/01/11 1:58 PM