Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
World Community Grid Forums
Category: Support Forum: Website Support Thread: wcgresults 2.29 |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 16
|
Author |
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2089 Status: Recently Active Project Badges: |
Hi Adri, Thanks for all the updates and thought being put into wcgresults. Just downloaded and tried version 2.31.0.9 and received this:-
line 1586 is :-
Oops! That line was there for a short while when testing and I deleted it afterwards, but I did not in the uploaded version. In the meantime I have uploaded a new version 2.31.3.3(*) and introduced a configurable variable RETRY_SLEEPING_TIMER that defaults to 90 seconds of sleeping time (preconfigured). See the section "CONFIGURE". Sorry for the confusion! Adri PS Thank you for reporting, Tony, else I wouldn't have uploaded this new version that fast. - avail=`perl -wne 'do { print && exit } if s/\s+"ResultsAvailable": "([^"]+)",\s+/$1/' - "(%d inactive file%s remaining)\n" [Edit 1 times, last edit by adriverhoef at Sep 27, 2022 9:19:23 AM] |
||
|
TonyEllis
Senior Cruncher Australia Joined: Jul 9, 2008 Post Count: 259 Status: Offline Project Badges: |
Adri, Just downloaded wcgresults from https://sourceforge.net/projects/wcgtools/files/ . It was still "VERSION: 2.31.0.9" - have commented out the errant line in that version for now... Was I meant to get 2.31.3.3 from somewhere else?
----------------------------------------
Run Time Stats https://grassmere-productions.no-ip.biz/
|
||
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2089 Status: Recently Active Project Badges: |
Adri, Just downloaded wcgresults from https://sourceforge.net/projects/wcgtools/files/ . It was still "VERSION: 2.31.0.9" - have commented out the errant line in that version for now... You're right, Tony, what a "" (slapping my forehead) on my side. I must have been "", answering your post and forgetting to upload the new version. I've checked and the new release 2.31.3.5 (just a few more text changes) is now in place. My apologies. Thanks for checking! Was I meant to get 2.31.3.3 from somewhere else? This is the only place I'm afraid. Sourceforge it is. |
||
|
TonyEllis
Senior Cruncher Australia Joined: Jul 9, 2008 Post Count: 259 Status: Offline Project Badges: |
Thanks Adri, now have Version 2.31.3.5 running on 4 systems - let's see how it runs... No stalled downloads for the last 11 hours - so will just have to wait.
----------------------------------------
Run Time Stats https://grassmere-productions.no-ip.biz/
|
||
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 1932 Status: Offline Project Badges: |
No stalled downloads for the last 11 hours - so will just have to wait. I don't think there have been any stalled downloads for anyone in the last +24h... Ralf [Edit 2 times, last edit by TPCBF at Sep 28, 2022 4:40:09 PM] |
||
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2089 Status: Recently Active Project Badges: |
Paul:
I will download and review the latest next week. Hope you have the time. I was a PL/I programmer for several years and IBM mainframe sysprog since, using REXX and various OEM languages for automation & tools. Aha! So there is the link with IBM! Being able to configure sleep time by parameter would be good. By now you may have noticed that I introduced a variable $RETRY_SLEEPING_TIMER to configure by yourself in the CONFIGURE section.Reporting PID on locked exit was aimed at identifying a possible stuck running task or failed one that terminated. Maybe this is something to include in the documentation(*), since there is no 100% guarantee that the file contains the expected text.A verbosity level for messages would also be welcome. Something to be put on the wishlist.BTW the V for version option is not included in the Usage output. I've left this out of the usage list at the time, because I found that the usage text was already long enough as it was. Not only that, none of my WCGtools mentions the option -V, unless it can be used for something else (wcglog does, since -V is used to exclude a pattern there).You might ask, how does wcglog report its version? Well, it does this when you do wcglog -h. So, why not standardize this and have all WCGtools report their version when you do programname -h? That's a good question. If everyone says this should be standardized, then I will go ahead with that. Should have included my crontab entry and output: Yes, this needed some time to settle down in my mind. I'm calling each line above, each pass through the loop, an 'iteration'; in a future version it will be present as e.g. "(total 2 iterations)".~/.bin/wcgresults -x >> /tmp/wcg_retry.log 2022-09-24 14:50:41 Retried 1 times. 2022-09-24 15:02:02 Retried 5 times. 2022-09-24 15:11:22 Retried 3 times. […] (some of these may have been manual runs). Adri |
||
|
|