Message boards : BOINC client : BOINC 6.11/6.12, change log and news.
Message board moderation
Previous · 1 · 2 · 3 · Next
Author | Message |
---|---|
Send message Joined: 29 Aug 05 Posts: 15573 |
Unless the version is available from http://boinc.berkeley.edu/download_all.php, it may well be an internal test-build. Else, wait for the developer for the Mac to call this one, please. |
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.10 released for testing for all platforms Howdy Folks, 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.11 released for testing for all platforms Rom Walton wrote: Howdy Folks, 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.12 released for testing for Windows, Macintosh and Linux Rom Walton wrote: Howdy Folks, 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.13 available for testing for all platforms Rom Walton wrote: Howdy Folks, 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.14 available for testing for all platforms. Rom Walton wrote: Howdy Folks, 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.15 available for testing for all platforms. 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.16 available for testing for all Windows. 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.17 available for testing for Windows and Linux. Rom Walton wrote: Skip this release. I'll have a new build out as soon as I can figure 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.18 available for testing for all platforms. Rom Walton wrote: I removed the incompatible code that prevented work-fetch from Rom Walton wrote: Howdy Folks, 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.19 available for testing for all Windows + Macintosh. Howdy Folks, 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.20 available for testing for Windows. 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.21 available for testing for Windows. 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.22 available for testing for Windows, Linux and Macintosh. Howdy Folks, 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.23 has been retracted from testing for Windows, Linux and Macintosh. Rom Walton wrote: URGENT |
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.24 available for testing for Windows. But don't install it, it'll give runtime errors on BOINC Manager on just about any system with Windows Vista or better. Wait for 6.12.25 |
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.25 available for testing for Windows. BOINC 6.12.23 available for testing for Linux and Macintosh. Rom Walton wrote: Howdy Folks, Rom Walton wrote: Okay, this build (6.12.25) should now be working on all supported versions of Windows. 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.26 available for testing for Windows, Linux and Macintosh. Rom Walton wrote: Howdy Folks, 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.27 available for testing for Windows, Linux and 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. Rom Walton wrote: Howdy Folks, 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
Send message Joined: 29 Aug 05 Posts: 15573 |
BOINC 6.12.28 available for testing for Windows, Linux and 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. 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 needs registration. 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. The actual change log was taken from the Alpha email list and the Trac Timeline repository changes check-ins. This disclaimer was written by the volunteer moderators of this forum and approved of by the BOINC development team. Change Log:
|
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.