Hey @pcarruscag and @bigfooted,

I was looking into why this PR has been stuck since January and traced the ReverseOMP failure back to a transient network error during the git submodule clone .

Verified Locally Today

Test	Command	Result
Eigen URL works	git clone https://gitlab.com/libeigen/eigen.git	Exit: 0
Pinned commit exists	git checkout d71c30...	Exit: 0
Eigen/Core present	ls Eigen/Core	Exit: 0

Note: local test was on a research HPC node

Conclusion

The January failure looks like a dropped connection mid-clone to me. The folder was left empty, which made it surface as a compilation error.

PR #2746 this week showed the identical pattern — same code, CI failed 5 consecutive times then passed on retry — suggesting CI intermittently drops GitLab submodule clones.

The code here was approved by @pcarruscag in October 2025. If it seems reasonable, would a maintainer be open to re-running the ReverseOMP check?