Integrated tests pose warnings #3242
Description
Describe the Testing Issue
warningtot2023_11_22_13_58.txt
relate to the issues of #2844 "On November 21, 2023, I collected all available PRs on GitHub, categorized them as the warningtot2023_11_22_13_58.txt, and identified certain warnings that may require contributors to address.
The first case is as follows:
PR #2998 by @Qianruipku has introduced some new warnings, although they appeared and disappeared before the latest introduction.
...
PR 3008
PR 2998 2023-10-09T07:20:18.4148669Z 1: [WARNING ] totalstressref cal=1409.56340100 ref=1409.54391900 deviation=-0.01948200
...up to now appear
- 101_PW_15_pseudopots_LibxcLDA
- 103_PW_15_CS_CF
- 103_PW_15_CS_CF_bspline
- 103_PW_OU_CS_CF
- 107_PW_outWfcPw
- 107_PW_outWfcR
- 108_PW_RE
- 108_PW_RE_MG
- 109_PW_CR_fix_ac
- 109_PW_CR_fix_b
- 109_PW_CR_fix_bc
- 109_PW_CR_fix_c
- 109_PW_CR_moveatoms
- 110_PW_SY
- 112_PW_dipole
- 112_PW_efield
- 113_PW_gatefield
- 115_PW_sol_H2O
- 120_PW_KP_MD_MSST
- 120_PW_KP_MD_MSST_level2
- 120_PW_KP_MD_NPT
- 120_PW_KP_MD_NVT
- 170_PW_MD_1O
- 170_PW_MD_2O
- 201_NO_KP_DJ_CF_CS_GaAs
- 204_NO_KP_AFM
- 270_NO_MD_1O
The second case is as follows:
PR #3178 @wenfei-li has introduced a new warnings as
...
PR 3176
PR 3178 2023-11-09T06:28:13.2550640Z 1: [WARNING ] etotref cal=-200.93490284 ref=-200.93404758 deviation=0.00085526
...up to now
- 101_PW_15_paw
The third case is as follows:
PR #3122 @YuLiu98 has introduced a new warnings as
...
PR 3139
PR 3122 2023-11-03T04:12:42.2978862Z 1: [WARNING ] totalstressref cal=763.26430700 ref=763.25719100 deviation=-0.00711600
PR 3144
PR 3145 2023-11-03T14:42:51.5758164Z 1: [WARNING ] totalstressref cal=763.26434700 ref=763.25719100 deviation=-0.00715600
...up to now
- 101_PW_upf201_uspp_NaCl
The fourth case is as follows:
PR #3175 @pxlxingliang has introduced some new warnings：but these warnings had appeared before and disappeared at some point.
...
PR 3172
PR 3175 2023-11-08T07:02:03.8821639Z 1: [WARNING ] totalforceref cal=5.19522000 ref=5.19483200 deviation=-0.00038800
PR 3134
PR 3177 2023-11-09T01:40:44.4158332Z 1: [WARNING ] totalforceref cal=5.19522000 ref=5.19483200 deviation=-0.00038800
...up to now
- 102_PW_BPCG
- 184_PW_BNDKPAR_SDFT_ALL
- 184_PW_BNDKPAR_SDFT_MALL
The fifth case is as follows:
PR #3081 by @maki49 has introduced some new warnings as:
...
PR 3105
PR 3081 2023-10-25T17:22:09.7680675Z 1: [WARNING ] etotref cal=-145.79150761 ref=-145.79681340 deviation=-0.00530579
PR 3108
PR 3109 2023-10-26T09:27:52.6434574Z 1: [WARNING ] etotref cal=-145.79150761 ref=-145.79681340 deviation=-0.00530579
...appear up to now
- 207_NO_KP_OHS_SPIN4
- 207_NO_KP_OTdH
- 213_NO_mulliken
The sixth case is as follows:
PR #3133 @WHUweiqingzhou The warning may refresh the ref.data to eliminate the warning.
...
PR 3127
PR 3133 2023-11-02T03:49:49.1430259Z 1: [WARNING ] totalstressref cal=4160.38232200 ref=4160.36613500 deviation=-0.01618700
...appear up to now
- 281_NO_KP_HSE
- 286_NO_KP_CR_HSE
- 803_PW_LT_bcc
- 810_PW_LT_fco
- 812_PW_LT_sm
The last case is as follows: Some warnings appear consistently because GitHub only supports data for up to three months. The warning may refresh the ref.data to eliminate the warning.
- 109_PW_CR
- 109_PW_CR_fix_a
- 109_PW_CR_fix_ab
- 109_PW_CR_fix_abc
- 116_PW_scan_Si2
- 116_PW_scan_Si2_nspin2
- 150_PW_15_CR_VDW3
- 601_NO_TDDFT_CO
- 801_PW_LT_sc
- 802_PW_LT_fcc
- 807_PW_LT_bct
update state by @hongriTianqi according to https://github.com/deepmodeling/abacus-develop/actions/runs/7318359302/job/19934906652 at 2023-12-25
Additional Context
Aotogetwarn.txt
the bash script that I have used to collect the warnings, in order to use it one need download some of the related PR test with zip file and run the bash in the linux shell.
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.