Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-21073

Unittests -l generates different result depend on the location where it is executed.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 7.0.4
    • Fix Version/s: 7.0.4
    • Component/s: unittests
    • Labels:
      None

      Description

      If I execute it outside from the /opt/HPCCSystems/bin directory like:
       /opt/HPCCSystems/bin/unittests -l
      it reports 31 test modules:
      01 : InternalStatisticsTest 02 : StringBufferTest   03 : Base58Test 04 : CDaliUtils 05 : CFileNameNormalizeUnitTest 06 : JlibSemTest    07 : JlibSetTestQuick   08 : JlibQuantileTest   09 : JlibWildMatchCore  10 : JlibMapping    11 : JlibIPTTest    12 : CryptoUnitTest 13 : ConfigMgr2ValidateXSDs 14 : CcdServerTest  15 : CcdFileTest    16 : StringSetTest  17 : InMemoryIndexTest  18 : StatsAggregatorTest    19 : MergeStatsTest 20 : WUDetailsMetaTest  21 : roxierowtests::RoxieRowAllocatorTests  22 : EclIR::EclIRTests  23 : roxiemem::RoxieMemTests    24 : roxiemem::RoxieMemHugeTests    25 : roxiemem::RoxieBufferTests 26 : IKeyManagerTest    27 : BloomTest  28 : EclRtlTests29 : SegmentMonitorTest 30 : ValueSetTest   31 : NBcdTest  
      If I do same inside the  /opt/HPCCSystems/bin like:
      pushd /opt/HPCCSystems/bin; ./unittests -l; popd
      then it reports 22 test modules only:
      01 : InternalStatisticsTest 02 : StringBufferTest   03 : Base58Test 04 : CDaliUtils 05 : CFileNameNormalizeUnitTest 06 : JlibSemTest    07 : JlibSetTestQuick   08 : JlibQuantileTest   09 : JlibWildMatchCore  10 : JlibMapping    11 : JlibIPTTest    12 : CryptoUnitTest 13 : ConfigMgr2ValidateXSDs 14 : roxiemem::RoxieMemTests    15 : roxiemem::RoxieMemHugeTests    16 : roxiemem::RoxieBufferTests 17 : IKeyManagerTest    18 : BloomTest  19 : EclRtlTests    20 : SegmentMonitorTest 21 : ValueSetTest   22 : NBcdTest  
      I presume it should be independent from the path and the test module lists should be identical.

      The problem is the generated lib path which is depend on the current execution path.

        Attachments

          Activity

            People

            • Assignee:
              attilavamos Attila Vamos
              Reporter:
              attilavamos Attila Vamos
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: