changing test 218

[BariumOxide13716]

Reminder

• Have you linked an issue with this pull request?
• Have you added adequate unit tests and/or case tests for your pull request?
• Have you noticed possible changes of behavior below or in the linked issue?
• Have you explained the changes of codes in core modules of ESolver, HSolver, ElecState, Hamilt, Operator or Psi? (ignore if not applicable)
  Due to an unexpected behavior of running parallelly with 2 cores as reported in outlying behavior when running with 2 cores for mixing kinetic energy density #6086, the integrate test 218 is deleted such that it does not use mixed kinetic energy density (calculations using which yield a different result with 2 cores compared with those with a different number of cores) during the test calculation.

Linked Issue

Concerned with #6086 but not yet resolved.

Unit Tests and/or Case Tests for my changes

N.A.

What's changed?

Integrate test 218 is removed.

Any changes of core modules? (ignore if not applicable)

N.A.

[mohanchen]

Do we have tests that use mixed kinetic energy density?

[mohanchen]

Sorry, I don't understand why we need to remove a test when we find a bug?

[BariumOxide13716]

Sorry, I don't understand why we need to remove a test when we find a bug?

Sorry for the confusion. The test that revealed this bug is likely to fail in the CI/CD. Because we have submitted an issue relating to this bug, we will try to fix this bug as we resolve the issue, and add the test back.

And to respond to the previous question on whether we had a test on mixed kinetic energy density, the test was not there until 4 days ago. @dyzheng was unable to make this test pass when he tried to merge from the develop branch. So now the plan is to remove the test, so the develop branch can be merged to other people's branches, meanwhile we will try to fix this bug.

[mohanchen]

Make sense, thanks for the explanation.

[mohanchen]

I found there is a conflict, should we fix it before merging the PR?

[BariumOxide13716]

I found there is a conflict, should we fix it before merging the PR?

Definitely. I'll update you when this conflict is resolved tmr. (Sorry for the delay.)

[mohanchen]

I found there is a conflict, should we fix it before merging the PR?

Definitely. I'll update you when this conflict is resolved tmr. (Sorry for the delay.)

OK, thanks.

[BariumOxide13716]

I found there is a conflict, should we fix it before merging the PR?

Definitely. I'll update you when this conflict is resolved tmr. (Sorry for the delay.)

OK, thanks.

The code should be in good shape and ready to merge now. Please feel free to approve and merge it anytime.