Ok - I ran 3.3.7 through the testing.
* cmake ..\eigen_3.3.7 -G "Visual Studio 15 Win64" -Thost=x64
* I later realized that VS also uses the 32-bit toolchain by default,
but I doubt it has a big effect here
* ctest -C Release -D Experimental
The complete build took about 22 hours. I flagged anything that took longer
than ten minutes (I calculated build time as the modified time of the test
minus the modified time of the previous test).
* array_reverse_8 (16 mins)
* geo_quaternion_2 (25 mins)
* geo_quaternion_4 (30 mins)
* mixingtypes_5 (12 mins)
* product_small_3 (11 mins)
* product_small_4 (23 mins)
* sparse_extra_1 (98 mins)
* sparse_extra_2 (215 mins)
* sparse_extra_3 (105 mins)
* sparse_product_1 (108 mins)
* sparse_product_2 (256 mins)
* sparse_product_3 (104 mins)
Not sure if that list forms a pattern. I will continue investigating when i get
a chance.
The actual tests took...12 mins. Only 1 failed.
Rob
________________________________
From: Rob Conde <[email protected]>
Sent: Monday, June 10, 2019 9:53 AM
To: [email protected]
Subject: Re: [eigen] Windows Testing Issues
Hey Edward,
I did try that quickly at one point for a single test but I don't remember
seeing a big difference, but I will try to do something more comprehensive.
When I get a chance (sigh) I will also see if I can distill a simple example
which i can report to the visual studio team. At this point I haven't spent
much time trying to find a pattern in the things that take a long time to
compile, if there is one, but that would be useful too I think.
Rob
________________________________
From: Edward Lam <[email protected]>
Sent: Monday, June 10, 2019 9:03 AM
To: [email protected]
Subject: Re: [eigen] Windows Testing Issues
Hi Rob,
On 6/10/2019 7:57 AM, Rob Conde wrote:
> This has been running for about 11 hours now (still on the build part).
> Obviously this is a visual studio issue, but I'm not sure when it was
> introduced. We're not seeing anything like this in the our usage of
> Eigen...although to a smaller degree it might be hard to tease out of the
> larger
> picture.
It might be worthwhile trying out the latest Visual Studio 2019 just to see if
there's any behaviour change.
-Edward
