Info | Message |
---|---|
1) Message boards : News : Minecraft@Home launched
Message 99521 Posted 28 Jun 2020 by chip |
It looks like these validation issues you experienced are caused by a limited number of AMD GPUs, we'll likely just need to add some compatibility support for them.No, a validate error happens when the contents of the result differ wildly from those of others. Like I said, all others I have seen use the CPU quite heavily, mine doesn't. I was paired against an AMD RX 580 and even there my result didn't validate. So something is off with my type of video card. And it isn't drivers, as I updated from 20.3.1 to 20.5.1 between tasks, on either side I didn't validate. We think it’s something to do with the way fprintf is handled differently. We’re rolling potential fixes over the next couple of days. Our validator is looking for a keyword in the stderr which is missing, presumably because of this issue. The strangest behaviour is; we see hosts which have been with us for a long time with similar cards, but half of their results are processed as expected (we see the expected output), however the others fail in exactly the same mode you experienced with no other discernible changes. (no probs, we all have one of those sometimes) |
2) Message boards : News : Minecraft@Home launched
Message 99519 Posted 28 Jun 2020 by chip |
Checkpointing is useless if the application isn't doing anything useful, only running to end in validate errors as it does on my AMD RX 5700 XT. Don't you read your own forums, well news thread? Hi Jord, I've had a read through the discussions on the news posts and have been implementing changes over the course of today. There's some working changes to the app to implement multi-gpu support and checkpointing. It looks like these validation issues you experienced are caused by a limited number of AMD GPUs, we'll likely just need to add some compatibility support for them. The remaining forums are live now to facilitate on-platform discussion, I've encouraged others behind the project to get involved with those discussions. |
3) Message boards : News : Minecraft@Home launched
Message 99474 Posted 27 Jun 2020 by chip |
Looks like I solved it. We moved to SendGrid for SMTP and I wrote some code to resend those BOINC-wide teams messages. Let me know if you got one. Checkpointing is coming in the next few days :) |
4) Message boards : News : Minecraft@Home launched
Message 99457 Posted 26 Jun 2020 by chip |
BOINC-wide teams is configured nowI noticed that, but didn't get the confirmation email about that. Normally this would send out an email to team founders saying "Team created on XXX", where XXX is your project name. It turns out our SMTP service ratelimited us. We’re likely going to use a new provider. I’m sure it’ll be acceptable if we find the messages which were unsent and artificially push them through. |
5) Message boards : News : Minecraft@Home launched
Message 99441 Posted 25 Jun 2020 by chip |
GPU-only for now, BOINC-wide teams is configured now, AMD was recently added so there are some teething issues |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.