BOINC 7 development discussion thread.

Message boards : BOINC client : BOINC 7 development discussion thread.
Message board moderation

To post messages, you must log in.

Previous · 1 . . . 5 · 6 · 7 · 8 · 9 · 10 · 11 · Next

AuthorMessage
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 73763 - Posted: 4 Nov 2016, 9:48:22 UTC - in response to Message 73762.  
Last modified: 4 Nov 2016, 9:48:46 UTC

Thanks for that, Christian. Mind posting the same to our email thread so everyone in that knows about that?

(Edit: signature)
ID: 73763 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 73770 - Posted: 4 Nov 2016, 20:08:13 UTC - in response to Message 73762.  

I also investigated about moving the dependency repositories to github and it seems that with the advent of git lfs (large file support) we are able to migrate. Github has a hard limit on file size (100MB) and some of the files in the dependency repos are bigger than that. I found a viable way to migrate the existing repos to lfs repos on github and will test this soon.


The quota limits of the free Git LFS could be a problem. From About storage and bandwidth usage:

All personal and organization accounts using Git LFS receive 1 GB of free storage and 1 GB a month of free bandwidth.


For the VS2013 repo the largest files are:
116037816 ./wxwidgets/mswin/x64/Debug/lib/vc_lib/wxmsw30ud_core.lib
 80756766 ./wxwidgets/mswin/Win32/Debug/lib/vc_lib/wxmsw30ud_core.lib
 79456656 ./wxwidgets/mswin/x64/Release/lib/vc_lib/wxmsw30u_core.lib
 68340262 ./wxwidgets/mswin/Win32/Release/lib/vc_lib/wxmsw30u_core.lib
 63582160 ./virtualbox/win/common.cab


Even though the limit for repos is 100 MB I think it would be best to move files that are close to 100 MB to LFS as well to let them have a bit room to grow. So lets say all four wx files are moved to LFS. That's about 340 MB total. wx was updated once so that makes 680 MB total.

VS2010 repo is even bigger. wx 3 was updated four times and then there's wx 2.8 a few times too. I'm not going to count how much total space they use.

Then there's the problem with the size of all the other files. From What is my disk quota?:

We recommend repositories be kept under 1GB each. This limit is easy to stay within if large files are kept out of the repository. If your repository exceeds 1GB, you might receive a polite email from GitHub Support requesting that you reduce the size of the repository to bring it back down.


VS2013 repo is below that, only about 650 MB. VS2010 repo on the other hand is huge, somewhere between 1.7 and 2 GB. (Large files included in both figures.) Even without large files there's good chances the VS2010 repo would result in such a request.
ID: 73770 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 74682 - Posted: 8 Dec 2016, 8:44:01 UTC

BOINC 7.6.33 is now recommended for Mac and Windows.
ID: 74682 · Report as offensive
Claggy

Send message
Joined: 23 Apr 07
Posts: 1112
United Kingdom
Message 75883 - Posted: 13 Feb 2017, 4:46:21 UTC

Since it's been five months since the 7.6 head has been worked on, and it was even earlier than when Boinc 7.6.33 was tagged,
I've gone and Cloned the Boinc repository, tagged a 7.6.34 release, and done a pull request back at the Boinc repository,

Claggy
ID: 75883 · Report as offensive
Arthur Lonnie Masson
Avatar

Send message
Joined: 2 Nov 15
Posts: 7
United States
Message 75927 - Posted: 14 Feb 2017, 21:26:23 UTC - in response to Message 75883.  

Does this mean that there will be a 7.6.34 release soon? If so, which OS platforms are targeted?
ID: 75927 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 75928 - Posted: 14 Feb 2017, 21:45:25 UTC - in response to Message 75927.  

No.

As Christian Beer answered to Claggy in Github:
Releasing a new client version is a multi-step process. At the start there is the version change commit and a git lightweight tag on that commit but then someone has to build official binaries for all platforms and package them into the respective installer bundles.

Technically what you submitted is the first step, someone else would need to create the git tag and build the official installers from that. Then begins the testing of these packages. Then this someone (usually called Release Manager) adds commits from master to the release branch and creates a new version and so on.

So unless there is a Release Manager who actually prepares and does a release, I don't see a reason to do the version change or tagging.

Also from a technical perspective this should all be done from within the BOINC repository because every PR always introduces a merge commit which should be avoided in the release branch (because it is very confusing later on).
ID: 75928 · Report as offensive
SnapShot

Send message
Joined: 20 Feb 17
Posts: 1
United States
Message 76036 - Posted: 20 Feb 2017, 0:38:47 UTC

I have been dealing with issues of BOINC performance declining based on using Task Manager as my reference. In the past three or more months I have found that the BOINC program when first loaded runs four to eight projects based on which computer and runs at the top nearly 100% of CPU performance. A week to a month later the amount of projects remain the same but the performance drops by 50% so these project tasks now run at near 49%. I noticed this first in the WCG totals over running the past near three years and so others that I have brought on board are telling me the same thing and getting the same drops in performance so it can not be the equipment but has to be the software. Others in a group I am in have come to me for best BOINC settings and their performance was doing very well and then dropped just in the past six months or so. I find that if I remove the BOINC program and reload it I get back to 100% and it runs that way for about a week to maybe over a month. I had others try this and watch their Task Manager and they claim they are getting the same reduction in performance and back up once they remove and reload the program. Just don't know what else to do or what is happening.
ID: 76036 · Report as offensive
Les Bayliss
Help desk expert

Send message
Joined: 25 Nov 05
Posts: 1654
Australia
Message 76037 - Posted: 20 Feb 2017, 2:46:04 UTC - in response to Message 76036.  

I don't know the answer(s), but there are several things that you'll be asked by those that do.
They're listed in this thread, which is a sticky in the Questions and problems section.
I'm not sure which part of it is currently relevant, but starting at the beginning may be best. And a link to one of your projects wouldn't hurt. :)
ID: 76037 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 76903 - Posted: 26 Mar 2017, 17:28:14 UTC

David Anderson wrote:
I released a new version of the client for Win.
Changes:

- An accumulation of enhancement/fixes in the manager and client since June 2016.
- The Vbox versions include VBox 5.1.18
- not code-signed (I didn't have the $200 needed to renew the certificate).
- built by me rather than Rom (hopefully I did it right).

Please give it a try.
Alpha testers can report bugs here: http://boinc.berkeley.edu/alpha/test_form.php

-- David
I'll add the change log notes as soon as I can figure out how to get them through SmartGit, the only program that seems to be working on my PC.
ID: 76903 · Report as offensive
boboviz
Help desk expert

Send message
Joined: 12 Feb 11
Posts: 410
Italy
Message 76921 - Posted: 27 Mar 2017, 11:06:18 UTC - in response to Message 76903.  

I'll add the change log notes as soon as I can figure out how to get them through SmartGit, the only program that seems to be working on my PC.


I think that open a new thread "7.7/7.8 Change Log and News" (as suggested in mailing list) will be great
ID: 76921 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 76926 - Posted: 27 Mar 2017, 12:02:28 UTC - in response to Message 76921.  

A separate thread about the new development version is what I had in mind anyway, but has nothing to do with the request by Charlie to add a separate branch and tag in gitHub. That's just done so all the development of the newer client doesn't happen in Master. But as far as I know, development always happened in Master, until the client was far enough along, that it would go into production numbering and get its own branch - in this case 7.8
But to get to 7.8 we first have to traverse a lot of 7.7s.
ID: 76926 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 76927 - Posted: 27 Mar 2017, 13:31:36 UTC - in response to Message 76926.  

It's going to be quite labour intensive to get the change logs out.

Because TortoiseGit doesn't work on my system - it's missing something due to which it doesn't show up in Windows Explorer at all - I have to resort to another Git GUI, in this case SmartGit. But however smart it may be, it's not smart enough to just give me a log printout of all the changes from a certain date or tag. So I would have to manually copy all the messages from the message window to Notepad, which with over 2,500 commits since June 2016 is going to be too much work for me.

I'll have to figure out another way to do this. Or give up.
ID: 76927 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5077
United Kingdom
Message 76928 - Posted: 27 Mar 2017, 14:12:18 UTC - in response to Message 76927.  

I only see 1109 commits...

My Tortoise is working (up to a point) - you have mail.
ID: 76928 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 79481 - Posted: 6 Jul 2017, 20:59:39 UTC

David Anderson wrote:
I released 7.8.0 for testing (Windows 32 and 64, with and without VBox).

Alpha testers: this is a potential public release candidate;
please test it thoroughly, including the VBox versions.

Changes relative to 7.7.2:

- Vbox installers have Vbox 5.1.22 rather than 5.1.18 (should work on Win 10)

minor changes:
- On startup, show alternate platforms
- On startup, show account manager name if using one
- Don't crash if can't open gui_rpc_auth.cfg
- Fix display of max disk usage

support for future features (not testable at this point):
- Add mechanism for account managers to send opaque data to schedulers
- Include peak FLOPS in GPU descriptions sent to AMs and schedulers
- Add GUI RPCs for read/write app_config.xml files (for BOINCTasks)

-- David


Charlie Fenton wrote:
BOINC 7.8.0 for Macintosh is available for testing.

In addition to the changes mentioned for Windows, the Mac build has extensive modifications to replace deprecated system calls with ones currently recommended by Apple, to ensure continued compatibility with future versions of Mac OS X. Please test thoroughly.

Cheers,
--Charlie Fenton
ID: 79481 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 80107 - Posted: 10 Aug 2017, 10:54:51 UTC

Charlie Fenton wrote:
Since I see that David has created the client_release/7.8/7.8.1 tag, I have built BOINC 7.8.1 with its installer for the Macintosh and posted it to the "Index of /dl" page.

Cheers,
--Charlie

See the change log post for the change log and links.
ID: 80107 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 80138 - Posted: 12 Aug 2017, 22:09:14 UTC

David Anderson wrote:
7.8.1 is now available for testing on Win and Mac.
The changes relative to 7.8.0 are:
- fix startup crash on Win 10
- upgrade to VBox 5.1.26, which is required on latest Win10 versions.

This is a release candidate; please test and report results soon.

Thanks -- David
ID: 80138 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 80559 - Posted: 29 Aug 2017, 20:21:29 UTC

David Anderson wrote:
A new client is available for testing on Win and Mac.
The changes relative to 7.8.1 are:
- fix slow startup problem on Win
- update translation files.

This is a release candidate.
Please report test results soon: https://boinc.berkeley.edu/alpha/test_form.php

Thanks --

David
Download links: here.
ID: 80559 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5077
United Kingdom
Message 80561 - Posted: 29 Aug 2017, 22:22:22 UTC - in response to Message 80559.  

But other - reported and fixed - problems are still present.

- the word 'daemon' is presented to users in the options dialog
- 'OK' is still used instead of 'Save' in the Computing preferences dialog
- GPU detection fails when 'boinc' is started from the command line, instead of 'boinc.exe'
ID: 80561 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 80579 - Posted: 30 Aug 2017, 16:07:17 UTC - in response to Message 80561.  

- the word 'daemon' is presented to users in the options dialog
Not sure which version of the manager you're running, but in the Berkeley 7.8.2 the 'daemon' part is gone again. Its new counterpart 'client' isn't there either for that matter.
ID: 80579 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5077
United Kingdom
Message 80583 - Posted: 30 Aug 2017, 16:59:20 UTC - in response to Message 80579.  

The version I downloaded last night:



ID: 80583 · Report as offensive
Previous · 1 . . . 5 · 6 · 7 · 8 · 9 · 10 · 11 · Next

Message boards : BOINC client : BOINC 7 development discussion 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.