isce-framework / isce-framework/isce3

ctest 77% tests passed, 36 tests failed out of 159 (Debian GNU/Linux 10 )

Open
#9 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
239
Forks
90
Avg merge
13d 1h
Merged PRs (30d)
5

Description

I am trying to install ISCE3 on a Debian GNU/Linux 10 machine. While checking the installation with ctest, I have encountered the following errors. Any help would be appreciated (LastTest.log ).

77% tests passed, 36 tests failed out of 159

Total Test time (real) =  53.97 sec

The following tests FAILED:
         97 - test.python.pybind.core.poly2d (Failed)
        102 - test.python.pybind.focus.backproject (Failed)
        104 - test.python.pybind.focus.presum (Failed)
        106 - test.python.pybind.geocode.geocodeSlc (Failed)
        107 - test.python.pybind.geocode.geocodeCov (Failed)
        108 - test.python.pybind.geocode.radar_grid_cube (Failed)
        111 - test.python.pybind.geometry.geo2rdr (Failed)
        112 - test.python.pybind.geometry.rdr2geo (Failed)
        113 - test.python.pybind.geometry.rtc (Failed)
        114 - test.python.pybind.geometry.metadata_cubes (Failed)
        115 - test.python.pybind.image.resamp (Failed)
        123 - test.python.pybind.signal.crossmul (Failed)
        126 - test.python.pybind.product.generic_product (Failed)
        133 - test.python.pybind.geometry.look_inc_from_sr (Failed)
        136 - test.python.pybind.antenna.el_pattern_est (Failed)
        138 - test.python.pkg.isce3.core.gpu_check (Failed)
        139 - test.python.pkg.isce3.signal.point_target_info (Failed)
        140 - test.python.pkg.isce3.unwrap.snaphu (Failed)
        141 - test.python.pkg.nisar.products.readers.attitude (Failed)
        142 - test.python.pkg.nisar.products.readers.orbit (Failed)
        143 - test.python.pkg.nisar.products.readers.raw (Failed)
        144 - test.python.pkg.nisar.workflows.crossmul (Failed)
        145 - test.python.pkg.nisar.workflows.focus (Failed)
        146 - test.python.pkg.nisar.workflows.stage_dem (Failed)
        147 - test.python.pkg.nisar.workflows.gcov (Failed)
        148 - test.python.pkg.nisar.workflows.geo2rdr (Failed)
        149 - test.python.pkg.nisar.workflows.geocode_insar (Failed)
        150 - test.python.pkg.nisar.workflows.gslc (Failed)
        151 - test.python.pkg.nisar.workflows.insar (Failed)
        152 - test.python.pkg.nisar.workflows.filter_interferogram (Failed)
        153 - test.python.pkg.nisar.workflows.bandpass_insar (Failed)
        155 - test.python.pkg.nisar.workflows.rdr2geo (Failed)
        156 - test.python.pkg.nisar.workflows.resample_slc (Failed)
        157 - test.python.pkg.nisar.workflows.unwrap (Failed)
        158 - test.python.pkg.nisar.workflows.antenna_parser (Failed)
        159 - test.python.pkg.nisar.antenna.beamformer (Failed)
Errors while running CTest

Most these failed tests has a common block of code

    from . import unwrap
/home/tools/isce/install/packages/isce3/unwrap/__init__.py:3: in <module>
    from . import snaphu
E     File "/home/tools/isce/install/packages/isce3/unwrap/snaphu.py", line 659
E       def scratch_directory(d: Optional[os.PathLike] = None, /) -> pathlib.Path:
E                                                              ^
E   SyntaxError: invalid syntax ```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached LastTest.log and the traceback in isce3/unwrap/snaphu.py at line 659, then reproduce the failures with ctest on Debian GNU/Linux 10. Trace how this error affects the listed Python tests and workflows; done means identifying the compatibility or installation cause and establishing the expected test result.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.