Message boards : BOINC client : BOINC 7.16 Change Log
Message board moderation
Author | Message |
---|---|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 7.16.5 available for testing for Windows, BOINC 7.16.6 available for testing for Macintosh. Disclaimer On development versions of BOINC: - Expect parts of it to be broken, or in the least to work in a different way than you are used to. - Expect work failures, deadline misses and losing all your accumulated work in progress, or not getting credit for your work due to unknown and unforeseen circumstances. - Only use it when you are willing to participate in the Alpha test program and do not mind sending (bug) reports in to the developers on the email list specially assigned for this purpose. - Due to the CUDA and OpenCL detection, your screen may flicker or turn off temporarily. This is normal. System Requirements where applicable � Windows XP/Vista/7/8/8.1/10, 64bit only. � Mac OS X versions 10.6.0 and above, 64bit only. � Linux, built for and current Fedora/Ubuntu/Debian/Redhat distributions, may work on others, 32bit and 64bit. REMINDER TO ALL ALPHA TESTERS: It's far easier for the developers to fix problems when you send message logs with the appropriate flags set. The main flags are: <cpu_sched_debug>: problems involving the choice of applications to run. <work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much). <rr_simulation>: problems involving jobs being run in high-priority mode. <sched_op_debug>: problems involving scheduler operations and other low level information. Use these flags from the cc_config.xml file. Report any problems you get with it to the Alpha email list. This list requires access to Google Groups, which may require a Gmail email address. To sign up with the group, click the "Apply to join group" button. Reporting bugs on this forum or any project's forum isn't very productive as the developers simply do not have time to scour through all forums looking for posts with your bug reports in them. While it may happen that we - other volunteers - forward your problem to them, history has shown it is quite difficult being the middle man in this when more information is needed from you. Hence why it's better for all concerned that you report the problem directly to the developers, who will come back directly to you when they need more information or better logs or to tell you that they've checked in a fix for the specific problem. Adding the possible bug to Github Issues is also an option. Github requires registration as well. The actual change log was taken from the Alpha email list and the Github Timeline repository changes check-ins, but it can happen that changes in the list are missing, double, or misplaced. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC volunteer development team. Preliminary Change Log 7.16.5 & 7.16.6
|
Send message Joined: 28 Jun 10 Posts: 2725 |
Time to see if the bug that causes 64bit version to crash under WINE as soon as I switch to advanced view has gone. |
Send message Joined: 28 Jun 10 Posts: 2725 |
Time to see if the bug that causes 64bit version to crash under WINE as soon as I switch to advanced view has gone. Still crashes when switching to advanced view. Also crashes if I click on notices tab. On a positive note, it will download and run work. (Don't think I had actually tested this before, but gave up on finding it crashed when I went to advanced view. Is it worth my joining the Google group and posting the unhandled exception message I get? (Part of me thinks someone must have done this before but maybe not? I don't know if there are any other projects apart from CPDN which sometimes go for long periods of time with Windows work but none for Linux?) |
Send message Joined: 29 Aug 05 Posts: 15573 |
Is it worth my joining the Google group and posting the unhandled exception message I get? Better post it in BOINC Github, if you haven't already. |
Send message Joined: 29 Aug 05 Posts: 15573 |
The only fix in this one is the up-to-date ca-bundle.crt certification file to allow contacting projects. None of the other bug fixes have made it into this one. |
Send message Joined: 30 Mar 20 Posts: 425 |
Just a simple question regarding BOINC 7.16.7 I upgraded two of my computers (Windows 8.1) from boinc_7.6.22_windows_x86_64.exe to boinc_7.16.7_windows_x86_64.exe. On both computers, in the files stderrgpudetect.txt, and stderrdae.txt, the following errors appears: 08-Jun-2020 13:48:55: Unrecognized XML tag '<android_debug>' in LOG_FLAGS::parse; skipping 08-Jun-2020 13:55:04: Unrecognized XML tag '<android_debug>' in LOG_FLAGS::parse; skipping Worth noting perhaps, is that I do not have anything with "Android" in my cc_config.xml file The upgrade went well otherwise, and I can't see that anything is wrong. Just curious why those errors appears. |
Send message Joined: 5 Oct 06 Posts: 5133 |
Because the old version put them there - which was a bug. The new version has the bug removed, so it's surprised by something that it knows isn't supposed to be there. Make a trivial change to the Event Log flags (Ctrl+Shift+F) and save it. Revert it again, if you wish. That writes a whole, new, clean copy of the file - and the problem's gone. |
Send message Joined: 30 Mar 20 Posts: 425 |
Because the old version put them there - which was a bug. The new version has the bug removed, so it's surprised by something that it knows isn't supposed to be there. Heh, That's what I did actually after I noticed the errors, so maybe that's why I never saw the Android stuff in cc_config.xml. I only looked in it after I did exactly what you said :-) Thanks Richard for the explanation. Edit: I went into my backup, and looked at the cc_config.xml from before I upgraded, and indeed it had the <android_debug> in it, |
Send message Joined: 29 Aug 05 Posts: 15573 |
Charlie Fenton, Mac developer wrote: I've released BOINC 7.16.9 for alpha testing. This is a Macintosh-only release, and as usual is available from https://boinc.berkeley.edu/download_all.php. Please report test results to https://boinc.berkeley.edu/alpha/test_form.php or this email list. |
Send message Joined: 27 May 16 Posts: 8 |
On a minimal Lubuntu system, 7.16.6 fails to get tasks because of the following banale error - Memory: 603.08 MB physical, 301.54 MB virtual Disk: 301.54 MB total, 159.46 MB free BOINC is using available RAM as if it were available DISK - the server reports insufficient disk to download a task. |
Send message Joined: 29 Aug 05 Posts: 15573 |
What is a minimal Lubuntu system? Because if BOINC says you have only got 300MB disk space, I doubt any project out there can make use of it. And what's with the memory of just 600MB? If you're running in a VM, make sure you set it up correctly, that it's using actual GB instead of MB values. |
Send message Joined: 27 May 16 Posts: 8 |
Total disk storage is precisely the same as available virtual memory. That's what made me suspicious. I have used both Lubuntu's recommended 8GB (fixed, not dynamic) and Ubuntu's recommended 10GB (fixed, not dynamic) - with the same result. I would have expected a 2GB difference in disk storage. 'Something' is looking at the wrong variable. Maybe Oracle VM ? I have a BOINC 7.16.11 system in Windows 10 2004 under the the same VM - available memory here is noted around 1000MB, disk around 24GB total, 4GB free.. Maybe Lubuntu ? I regret I am totally new to it - I wouldn't know where to look for state variables there. I hope you have the time and inclination to verify this detail in BOINC 7.16.6 - or refer to your partners at Oracle. Someday I'll get my Pi farm ! |
Send message Joined: 29 Aug 05 Posts: 15573 |
Nice, but let's start at the beginning shall we? What is the actual system you run it on? Do you run Linux in a VM? If so which one? Have you tried a different one? Have you set up the VM yourself, or does it come as a package? or refer to your partners at OracleYou mean the makers of VirtualBox? They're not our partners. BOINC ships a version of VirtualBox included in one of the installers as an optional download, because we know the version that's included works with BOINC and all the projects that use VirtualBox. Not all VBox versions work well with all projects. |
Send message Joined: 27 May 16 Posts: 8 |
Sorry I haven't described the problem good enough. |
Send message Joined: 27 May 16 Posts: 8 |
Nice, but let's start at the beginning shall we? That's why I wouldn't dream of any other - it's BOINC's Oracle's version of VirtualBox I've used. I respect that it's important for researchers to eliminate 'red herrings'. Please take this problem seriously - it is not a mirage. There are many levels involved, to which I certainly do not not have access. Please find the source |
Send message Joined: 28 Jun 10 Posts: 2725 |
I have a BOINC 7.16.11 system in Windows 10 2004 under the the same VM - available memory here is noted around 1000MB, disk around 24GB total, 4GB free.. Not sure I am understanding the question. Does that mean you have two instances of BOINC running concurrently? If so, I suspect this may be the root of the problem. |
Send message Joined: 29 Aug 05 Posts: 15573 |
Windows 10 isn't a system. Windows 10 is only the operating system, it runs on hardware.What is the actual system you run it on? Again, what is your system? CPU, memory amount, operating system (not the one running in the VM, but the one runing the VM) Else please post the first 40 lines of your BOINC start up messages. I do hope this is something that got lost or went wrong in translation. Because I doubt you purposely want to insult me? May I remind you that I am just a volunteer helping out on these forums and that I will expect a bit of the same courtesy and professionalism in answers as I am giving you in me trying to help you out of my own free choice? Because if you cannot display that bit of courtesy, I will immediately cease my attempts to help you, put you on ignore and hope that someone else will step in to try to help you.Have you tried a different one? Have you set up the VM yourself, or does it come as a package?I followed Oracle and filled in the blanks. I'm a newbie in Linux - I don't know what else to do. You followed Orcale how? From a link? If so which one? Else, how did you set up the VM? What all runs in your VM? Only Linux, or Windows 10 as well? That's why I wouldn't dream of any other - it's BOINC's Oracle's version of VirtualBox I've used.Do know that it's not necessary to run BOINC in a VM. VirtualBox is shipped with versions of BOINC to allow projects that use it to immediately run their Linux VM and tasks on your computer. But BOINC is outside of that VM. So you run your normal operating system on your computer, in that you install BOINC and VirtualBox. Then when you add a project that requires VirtualBox, the project will use it and run its own Linux and tasks inside VirtualBox. BOINC just monitors this and shows real time information on the tasks running inside the VM. Not all projects use VirtualBox. So you can also just download & install BOINC without VirtualBox. So what was your intention? |
Send message Joined: 27 May 16 Posts: 8 |
Sorry Jord to have wasted your time. It has become clear to me that BOINC can't find the the virtual disk that Oracle has allocated to the virtual machine that Lubuntu runs on. My problem almost certainly arises from some error in my VM setup. |
Send message Joined: 26 Jun 14 Posts: 28 |
When will BOINC 7.16.16 (x64) be available for beta testing. It has been sitting on the beta d/l site since 27 Oct, but when I reported my results to BOINC Alpha, I was rudely shot down for the reporting as it was still in alpha testing and the installer was not ready for beta. Another question -- In of all the years that I've been beta testing, why was this even on the beta d/l site especially since the installer wasn't ready? |
Send message Joined: 29 Aug 05 Posts: 15573 |
the beta d/l sitehttps://boinc.berkeley.edu/dl/?C=M;O=D isn't a beta download site, it's the BOINC installer archive, all installers - even bad ones - end up there. |
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.