Message boards : Questions and problems : When is version 7.0.26 going to be released
Message board moderation
Author | Message |
---|---|
Send message Joined: 12 Apr 12 Posts: 19 |
According to a post made on : http://boinc.berkeley.edu/dev/forum_thread.php?id=7463 version 7.0.26 was going to be released on the 14 of April however it still hasn't been released for linux users yet can a rough estimate time be available to linux users so that we can have a rough outline of the time it takes. For Linux users if you have a computation error it is caused by something in BOINC version 7.0.24 so roll back temporarily to version 6.12.33 until the update has been released |
Send message Joined: 29 Aug 05 Posts: 15556 |
The developer ran into difficulties building the new libCURL, OpenSSL, Zlib and Sqlite3 libraries since there are projects out there that started dropping support for the program they were originally built with. As such he's rebuilding everything with a new version, which is slowing it all down. As I understand it, the plan is to release .26 on all platforms with bug-fixes for all in them. Somewhere this week. |
Send message Joined: 6 May 06 Posts: 287 |
A 7.0.26 tag has been created so the berkeley version shouldn't be too far away. Once it's released if you don't want to/can't use the berkeley version you will have to bug your distro's devs for a version bump, or you can try your hand at compiling it yourself following these instructions. CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1 |
Send message Joined: 5 Oct 06 Posts: 5125 |
A 7.0.26 tag has been created so the berkeley version shouldn't be too far away. Once it's released if you don't want to/can't use the berkeley version you will have to bug your distro's devs for a version bump, or you can try your hand at compiling it yourself following these instructions. Windows and Mac versions are available now in the download directory, and the Windows ones (tested both 32-bit and 64-bit) seem to be running OK. Hopefully the Linux version will appear in the same place soon. |
Send message Joined: 29 Aug 05 Posts: 15556 |
.26 is available for all platforms now. See the change log thread for change log and links to binaries. |
Send message Joined: 6 May 06 Posts: 287 |
According to a post made on : http://boinc.berkeley.edu/dev/forum_thread.php?id=7463 version 7.0.26 was going to be released on the 14 of April however it still hasn't been released for linux users yet can a rough estimate time be available to linux users so that we can have a rough outline of the time it takes. For Linux users if you have a computation error it is caused by something in BOINC version 7.0.24 so roll back temporarily to version 6.12.33 until the update has been released Please test the new version and report whether it resolves your issue or not. CIC1=CC=C(C2=N[C@@H](CC(OC(C)(C)C)=O)C3=NN=C(C)N3C4=C2C(C)=C(C)S4)C=C1 |
Send message Joined: 12 Apr 12 Posts: 19 |
No it fixed errors with ABC@home but now the exact same error is happening in eOn, so whatever the problem is I think the devs need to go back to the drawing board and start all over or find the portion of the code that involves error number -193 |
Send message Joined: 29 Aug 05 Posts: 15556 |
No it fixed errors with ABC@home but now the exact same error is happening in eOn It could well be a problem at eON. If other projects now no longer show this behaviour, yet one more does, it's probably something weird in their code. Also, the exit code is 193, not -193. Were it -193, it would be a BOINC client error code. Now that it is a positive error code, it's a science application error code. There's also no need to keep pressing on about it, I have forwarded your new thread on to development already. They're already busy figuring out why many people experience exit code 1 errors all of a sudden on a variety of projects & hardware. |
Send message Joined: 12 Apr 12 Posts: 19 |
what is exit code 1 again? |
Send message Joined: 29 Aug 05 Posts: 15556 |
Anything between "the application terminated due to unknown causes" to "the GPU you have installed is broken". It depends on whether the project added error coding or not. T4T for instance has only got exit code 1 as their error, doesn't matter what error you get there. Thus very difficult to track. |
Send message Joined: 12 Apr 12 Posts: 19 |
I went back to the jobs that were on version 7.0.24 and it had exit code 193 on ABC@home and it was the exact same exit code on 7.0.26 so I assumed that the problem still existed thus I made a new thread |
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.