Discussion related to cado-nfs

[Emmanuel Thomé <Emmanuel.Thome@inria.fr>]

Yes please. I mean, it's not a stringent requirement in general, but for
the matter at hand, you're indeed crossing an incompatibility boundary
(or so I guess).

STDOUT was added in WUs as a consequence of commit a4fc0715dc (march
2020), which provides a fix to 
https://gitlab.inria.fr/cado-nfs/cado-nfs/-/issues/21718

So any pre-march2020 client will choke on WUs sent out from a
post-march2020 server. Sorry for that.

Cheers,

E.

On Sat, Aug 22, 2020 at 09:05:28PM +0000, Ed Hall wrote:
> Hi Team,
> I'm trying to use the latest commit that was made today and the server is 
> sending out WUs and then waiting for timeout:
> Info:HTTP server: 192.168.0.77 Sending workunit 
> alicado_polyselect1_36000-40000 to client alicado99.77
> But, the clients are showing Errors:
> 2020-08-22 16:52:21,906 - INFO:root:Opened URL 
> http://math99.local:13531/cgi-bin/getwu?clientid=alicado99.77 after 290.0 
> seconds wait
> 2020-08-22 16:52:21,906 - ERROR:root:Invalid workunit file: Error: key 
> STDOUT not recognized
> 2020-08-22 16:52:21,907 - INFO:root:Removing workunit file 
> download/WU.alicado99.77
> 2020-08-22 16:52:21,907 - INFO:root:Downloading 
> http://math99.local:13531/cgi-bin/getwu?clientid=alicado99.77 to 
> download/WU.alicado99.77 (cafile = None)
> 
> Do I need to run the same commit on the clients for this revision to work?
> I have saved a copy of the working directory, but I'm not sure where to 
> upload/attach which files.
> 
> Sincerely,Edwin Hall

> _______________________________________________
> Cado-nfs-discuss mailing list
> Cado-nfs-discuss@lists.gforge.inria.fr
> https://lists.gforge.inria.fr/mailman/listinfo/cado-nfs-discuss