Necessary Maintenance #10358
artapp_basicOptions_print_t should be less strict
The above-mentioned test currently compares its output against a reference. This test can fail if unexpected modules are present in
LD_LIBRARY_PATH such as, for instance, when the art suite is part of an MRB working area.
The test should be reconfigured to test for the presence of expected fragments of output rather than comparing against a rigid reference.
#7 Updated by Lynn Garren about 4 years ago
This bug makes it impossible to build artextensions in the same build as the art suite, as the tests are guaranteed to fail. This bug is one piece that needs to be fixed for the stated goal of building larsoft against a new release of art after art is tagged and before the official art release build begins.
#9 Updated by Kyle Knoepfel about 4 years ago
Although this issue proper has been resolved, it points to another bug--specifically that if experiments do not adopt the library-naming convention as in
art, then an exception will be thrown whenever
LibraryManager::getSpecsByPath is called on a path that does not follow that convention. I have therefore created a new issue (#10407) to remove the exception throwing from that function.
Implemented with art:4c08288.