You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You are asking a very good question, @tanishy7777 .
I haven't looked at tests or the code, I only noticed that they seem to take a very long time compared to other tests. Given that the new guesser code is a recent addition (in 2.8.0), we should look at the impact that this code has. The first step would be understanding why they take so long: are the tests written in a complicated way and could be shortened or is the underlying guesser code slow?
I ran cProfiler(thrice to make sure of the results) on these test functions on my local system
The test_guess_topology_objects_out_of_order_init and test_guess_topology_objects_out_of_order_guess take about 5 seconds each and test_guessing_angles_respects_bond_kwargs takes about 25 seconds.
I have attached the output below. I am not sure what is causing it to take so long on github CI. @orbeckst
Expected behavior
Tests run reasonably quickly in our CI (let's say, faster than ~20 seconds).
Actual behavior
The top 3 slowest tests are all related to guessing functionality and take between 25 and 100 seconds. E.g. from https://github.com/MDAnalysis/mdanalysis/actions/runs/12399640935/job/34615007364?pr=4729 :
The text was updated successfully, but these errors were encountered: