![]() |
Taking 157_113m1.
|
[QUOTE=swellman;515104]Done, but please note the name was changed to 180__741_5m1 since your reservation was posted.[/QUOTE]
The queue is still stuck. From past experience, I'd guess that changing the names was not sufficient. There are most likely still a bunch of bad work units being handed out, and since they don't get completed they will keep being handed out until they are deleted from the queue. I think Greg will have to intervene here. |
He has been notified. It hung up yesterday I think.
|
[QUOTE=swellman;515129]He has been notified. It hung up yesterday I think.[/QUOTE]
I'm pretty sure it was hung up all weekend, and possibly on Friday as well. But in any case, something is happening now, but I don't think it's the correct thing. Work units for 16097_59m1 are not being fully generated, and they appear to be just dribbling out to sievers. In the past I think the only way to clear this condition was to remove and re-add the offending composite. And that will probably also require Greg to cancel more work units. |
[QUOTE=jyb;515170]I'm pretty sure it was hung up all weekend, and possibly on Friday as well.
But in any case, something is happening now, but I don't think it's the correct thing. Work units for 16097_59m1 are not being fully generated, and they appear to be just dribbling out to sievers. In the past I think the only way to clear this condition was to remove and re-add the offending composite. And that will probably also require Greg to cancel more work units.[/QUOTE] It’s been like this since Friday GMT evening. |
7p6_343 factored
[CODE]p56 factor: 54930848491816914651602322926979712763280364051646515679
p161 factor: 48721016122602074241812062630899845104508868809824174353918186580339649897172471480277716929045436802310924549808217616750057453987771441393242540845936956125513[/CODE] 207M unique relations built a 10.4M matrix using TD=124. (128 failed) Solve time about 74 hours. (-t 4) Log at: [url]https://pastebin.com/NvLpJnR8[/url] |
[QUOTE=jyb;515170]I'm pretty sure it was hung up all weekend, and possibly on Friday as well.
But in any case, something is happening now, but I don't think it's the correct thing. Work units for 16097_59m1 are not being fully generated, and they appear to be just dribbling out to sievers. In the past I think the only way to clear this condition was to remove and re-add the offending composite. And that will probably also require Greg to cancel more work units.[/QUOTE] Well 16097_59m1 seems to have gone fine, but the queue is stuck again. It's still trying to hand out work units for "180...741_5m1". Did Greg ever respond about canceling those? |
Just noticed this. Any time a number is deleted from the queue with WUs already generated, PM me to let me know to delete those WUs. Thanks!
|
7m4_343 completed - 154 hours for 12.1M matrix (TD=140)
[CODE]p87 factor: 326163360893917573940754941112111106910065198342646087449451166480607495848058310864081 p151 factor: 1392089526895321890831569495471862039543602568086606760583954380891901410842090981222516233313489937027814992966963015940510414214890891321873683216209[/CODE] [url]https://pastebin.com/PSqU8t88[/url] |
Advisory to not download any post processing jobs between 06 May 2019 00:00:00 (UTC) and 07 May 2019 00:00:00 (UTC) due to NFS@Home participating as a project on the Boinc Penthalon 2019. I’ll post the other 4 days where the server will be hit hard. Thank you.
|
38371_53m1 factored
[CODE]p71 factor: 40135128964809753211144279903232204726508324412399447394116402290648193
p168 factor: 581632643982042746926416995043172648456236366985279128580945140988893457436390017889606938047108610312004950810887563357845695783188512997519415526568972530142826106841[/CODE] 194M unique relations built a 16.4M matrix using TD=116. (120 failed) Solve time about 198 hours. (-t 4) Log at: [url]https://pastebin.com/Ah7ddD6e[/url] |
| All times are UTC. The time now is 22:39. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.