The weekly test of interface to DPGEN is failed at 20241016

[pxlxingliang]

Describe the Testing Issue

At 20241016, the test of interface to dpgen is failed.

https://app.bohrium.dp.tech/abacustest/?request=GET%3A%2Fapplications%2Fabacustest%2Fjobs%2Fsched-abacustest-interface-test-ade2fe

The error message is:

Traceback (most recent call last):
  File "/opt/mamba/bin/dpgen", line 8, in <module>
    sys.exit(main())
  File "/opt/mamba/lib/python3.10/site-packages/dpgen/main.py", line 255, in main
    args.func(args)
  File "/opt/mamba/lib/python3.10/site-packages/dpgen/data/gen.py", line 1583, in gen_init_bulk
    coll_abacus_md(jdata)
  File "/opt/mamba/lib/python3.10/site-packages/dpgen/data/gen.py", line 1245, in coll_abacus_md
    _sys = dpdata.LabeledSystem(oo, type_map=type_map, fmt="abacus/md")
  File "/opt/mamba/lib/python3.10/site-packages/dpdata/system.py", line 183, in __init__
    self.from_fmt(
  File "/opt/mamba/lib/python3.10/site-packages/dpdata/system.py", line 220, in from_fmt
    return self.from_fmt_obj(load_format(fmt), file_name, **kwargs)
  File "/opt/mamba/lib/python3.10/site-packages/dpdata/system.py", line 1113, in from_fmt_obj
    data = fmtobj.from_labeled_system(file_name, **kwargs)
  File "/opt/mamba/lib/python3.10/site-packages/dpdata/plugins/abacus.py", line 66, in from_labeled_system
    return dpdata.abacus.md.get_frame(file_name)
  File "/opt/mamba/lib/python3.10/site-packages/dpdata/abacus/md.py", line 175, in get_frame
    coords, cells, force, stress = get_coords_from_dump(dumplines, natoms)
  File "/opt/mamba/lib/python3.10/site-packages/dpdata/abacus/md.py", line 88, in get_coords_from_dump
    np.array([float(i) for i in dumplines[iline + 3 + ix].split()[0:3]])
  File "/opt/mamba/lib/python3.10/site-packages/dpdata/abacus/md.py", line 88, in <listcomp>
    np.array([float(i) for i in dumplines[iline + 3 + ix].split()[0:3]])
ValueError: could not convert string to float: 'LATTICE_CONSTANT:'

The error message show that the function of dpdata to get value from MD is destroyed.

Additional Context

No response

Task list for Issue attackers (only for developers)

• Understand the testing issue described by the developer.
• Review the specific test case, expected and actual results, and any error messages.
• Identify the root cause of the test failure or issue.
• If a possible solution is suggested, evaluate its feasibility and effectiveness.
• Implement a fix for the test failure or issue, or create a new test case if needed.
• Verify that the fix resolves the testing issue and the test case passes.
• Review and update any relevant documentation, such as test plans or user guides.
• Ensure the testing issue is resolved and close the ticket.
• Share any lessons learned or best practices with the team to prevent similar issues in the future.