| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Website Support
Thread: Results Status list oddity |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This observation has me scratching my head. Basically, it's this. Earlier today, I was filtering my Results Status by Device: Tree3, Status: In Progress, Project: All, giving 18 workunits (across one and a bit pages). I noticed that the list sorted by Return Time was different from that sorted by Sent Time. The reason I noticed was because I had 4 beta units running on that machine and only 3 beta units were listed when sorted by Return Time (but all 4 when sorted by Sent Time). Both lists still showed 18 workunits, so something else was changing as well. No new results were reported while I was observing this.
In detail, below is the list sorted by Return Time. The blank line denotes the division between Page 1 and Page 2. It takes a lot of concentration, or an Excel spreadsheet, to spot that all 3 units on Page 2 are in fact duplicates of some on Page 1! So do I need to reinstall Windows (as the saying goes), or does a server need rebooting, or ... ? BETA_ MDDS_ 000000012_ x4e78_ HCV_ 2aJFH1_ NS5Bpol_ DelRNA_ 0037_ 1-- Tree3 In Progress 13/05/16 03:22:16 23/05/16 03:22:16 0.00 / 0.00 0.0 / 0.0 BETA_ MDDS_ 000000012_ x4e78_ HCV_ 2aJFH1_ NS5Bpol_ DelRNA_ 0034_ 1-- Tree3 In Progress 13/05/16 03:22:16 23/05/16 03:22:16 0.00 / 0.00 0.0 / 0.0 HST1_ 002072_ 000024_ AT0008_ T325_ F00049_ S00003_ 0-- Tree3 In Progress 12/05/16 20:33:14 22/05/16 20:33:14 0.00 / 0.00 0.0 / 0.0 HST1_ 002072_ 000029_ AT0008_ T325_ F00054_ S00003_ 0-- Tree3 In Progress 12/05/16 20:33:13 22/05/16 20:33:13 0.00 / 0.00 0.0 / 0.0 HST1_ 002072_ 000042_ AT0008_ T325_ F00067_ S00003_ 1-- Tree3 In Progress 12/05/16 20:33:14 22/05/16 20:33:14 0.00 / 0.00 0.0 / 0.0 HST1_ 002072_ 000012_ AT0008_ T325_ F00037_ S00003_ 1-- Tree3 In Progress 12/05/16 20:33:13 22/05/16 20:33:13 0.00 / 0.00 0.0 / 0.0 HST1_ 002072_ 000023_ AT0008_ T325_ F00048_ S00003_ 0-- Tree3 In Progress 12/05/16 20:33:13 22/05/16 20:33:13 0.00 / 0.00 0.0 / 0.0 HST1_ 002041_ 000067_ AC0017_ T001_ F00039_ S00002_ 0-- Tree3 In Progress 12/05/16 07:33:09 22/05/16 07:33:09 0.00 / 0.00 0.0 / 0.0 HST1_ 002040_ 000065_ AC0009_ T001_ F00100_ S00002_ 1-- Tree3 In Progress 12/05/16 07:03:06 22/05/16 07:03:06 0.00 / 0.00 0.0 / 0.0 HST1_ 002039_ 000053_ AC0001_ T001_ F00653_ S00002_ 0-- Tree3 In Progress 12/05/16 06:33:07 22/05/16 06:33:07 0.00 / 0.00 0.0 / 0.0 HST1_ 002039_ 000061_ AC0001_ T001_ F00661_ S00002_ 0-- Tree3 In Progress 12/05/16 06:33:06 22/05/16 06:33:06 0.00 / 0.00 0.0 / 0.0 HST1_ 002039_ 000047_ AC0001_ T001_ F00647_ S00002_ 1-- Tree3 In Progress 12/05/16 06:33:07 22/05/16 06:33:07 0.00 / 0.00 0.0 / 0.0 HST1_ 002039_ 000013_ AC0001_ T001_ F00613_ S00002_ 1-- Tree3 In Progress 12/05/16 06:33:06 22/05/16 06:33:06 0.00 / 0.00 0.0 / 0.0 HST1_ 002039_ 000066_ AC0001_ T001_ F00666_ S00002_ 0-- Tree3 In Progress 12/05/16 06:33:06 22/05/16 06:33:06 0.00 / 0.00 0.0 / 0.0 HST1_ 002039_ 000049_ AC0001_ T001_ F00649_ S00002_ 1-- Tree3 In Progress 12/05/16 06:33:06 22/05/16 06:33:06 0.00 / 0.00 0.0 / 0.0 HST1_ 002039_ 000066_ AC0001_ T001_ F00666_ S00002_ 0-- Tree3 In Progress 12/05/16 06:33:06 22/05/16 06:33:06 0.00 / 0.00 0.0 / 0.0 HST1_ 002039_ 000049_ AC0001_ T001_ F00649_ S00002_ 1-- Tree3 In Progress 12/05/16 06:33:06 22/05/16 06:33:06 0.00 / 0.00 0.0 / 0.0 BETA_ MDDS_ 000000012_ x4e78_ HCV_ 2aJFH1_ NS5Bpol_ DelRNA_ 0037_ 1-- Tree3 In Progress 13/05/16 03:22:16 23/05/16 03:22:16 0.00 / 0.00 0.0 / 0.0 |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
What If... you hit the Time Due part of the header instead of Return Time? I'd imagine there's a null value in the actual Return Time field [unless Deadline field and Return Time double act... would have to visit the API to see]
----------------------------------------Edit: No, Return Time and Deadline are separate fields... Return Time is null. [Edit 1 times, last edit by SekeRob* at May 13, 2016 12:36:25 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hehe, I did record that as well. By Time Due gives a list that is identical to that sorted by Sent Time.
|
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
That works if all have the same deadline time of 10 days, but I'd expect if there's beta in there, or a mix of 10/7/4/repair days deadlines, the positions shift.
Because RT is null, suppose it knows in your original case page 2 is 3 records, then picks up a random or first 3 hits set. Just a weird thing getting highlighted because you filtered on IP only. |
||
|
|
HopeSoloFan
Cruncher Joined: Jul 17, 2011 Post Count: 4 Status: Offline Project Badges: 
|
No new problem, it was reported at least twice in 2015:
https://secure.worldcommunitygrid.org/forums/...ead_thread,37841_offset,0 http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,38000_offset,0 In my opinion, problem remains unsolved. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks, I'd forgotten about those reports.
|
||
|
|
|