On Tuesday, 28 April 2020 23:49:09 UTC+1, Cactus wrote: > > On 28/04/2020 23:28, 'Bill Hart' via mpir-devel wrote: > > You may be right, but I don't see where your files are in our repo: > > > > https://github.com/wbhart/flint2 > > > > This would be better discussed on the flint list as Isuru Fernando could > > chime in. He understands CMake much better than I do. I don't want to > > make assertions about it, as they often prove to be wrong. > > > > Perhaps you could open a ticket with your observations on my Flint repo? > > I don't know a lot about CMake but I haave taken a look and, as far as I > can see, it is no longer dependent on my build files. > > But the Appveyor script in the Flint root directory DOES run my build > system and is not hence testing the output of the CMake build. > > So if you are relying on Appveyor you will be running my out of date > build and judging its output rather than the CMake build output. > > I'll ask about this on your repo. > > Brian >
I have updated my build options to match those used in the CMake build and the two earlier access violation failures no longer occur. But all the hanging tests are the same. I used a one minute timeout, which I think is reasonable. -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mpir-devel/a663ccd9-cffe-48e7-bb64-8b667e8459dc%40googlegroups.com.
