Re: [boinc_dev] [boinc_projects] BOINC - October 2017 VirtualBox and VBoxWrapper updates

2017-11-06 Thread Laurence Field

Hi Juha,


On 06/11/17 16:48, Juha Sointusalo wrote:



The reason I tested on LHC is that I wanted to test on real world 
apps, LHC has real world apps and I have already signed up there. 
That's all. Maybe LHC-dev would have been better choice or maybe I 
should have asked you for permission first but at that time the risk 
of VirtualBox 5.2 acting bad and tasks returning bad science results 
seemed low enough.
I just wanted to make sure you weren't waisting your time. Using either 
project is fine and no need to ask for permission.


Cheers,

Laurence
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates

2017-11-06 Thread Jacob Klein
David:

I saw your updated 26200 zip files from last night, and I'll call them "Release 
3" (since you keep reusing the same filenames).

I just concluded my testing of this "Release 3" 26200 version, and everything 
that I tested worked well. LHC VMs are able to resume in 5.2, and start new 
5.2. RNA World VMs are able to resume in 5.2. And stderr.txt was using correct 
version numbering.

May I recommend this version for Christian to consider using on RNA World? [I 
ask in case you are planning additional changes before deeming this version 
ready].

Let me know,
Thanks,
Jacob


From: Rom Walton 
Sent: Sunday, November 5, 2017 9:30 PM
To: David Anderson; Jacob Klein; Juha Sointusalo
Cc: BOINC Developers Mailing List; Boinc Projects; BOINC Alpha
Subject: RE: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates


version.h and version.h.in



- Rom



From: David Anderson [mailto:da...@ssl.berkeley.edu]
Sent: Sunday, November 5, 2017 6:08 PM
To: Jacob Klein ; Juha Sointusalo 

Cc: Rom Walton ; BOINC Developers Mailing List 
; Boinc Projects ; 
BOINC Alpha 
Subject: Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates



Rom,
Where does that version # (7.9.26197.0) come from?
-- D

On 11/5/2017 5:08 PM, Jacob Klein wrote:

David:

I tested this "Release 2" version of the 26200 wrapper. We're very close.



The good:

- The crashes starting LHC tasks on 5.2, and crashes resuming RNA World tasks 
on 5.2, appear to be resolved. No more crashes. I suspect Release 1 had the 
stale tlb file.

The bad - *2* issues:

- The "File Version" of the exe is still incorrect, and is being written to 
stderr.txt. We need to fix this, so we can keep track of what version of the 
wrapper is being used at points in the log.

- The x86 version will need rebuilt too, with the fixes.



Once you get that "File Version" resolved, maybe consider doing another version 
bump to 26201, for reasons of sanity :) Then let me know when to retest it - 
I'm getting good at it.



Thanks,

Jacob





From: Jacob Klein 
Sent: Sunday, November 5, 2017 5:37 PM
To: David Anderson; Juha Sointusalo
Cc: Rom Walton; BOINC Developers Mailing List; Boinc Projects; BOINC Alpha
Subject: RE: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates



Thanks David, I don't suppose there's any chance you could test, too, to see if 
you can get any repro? Wishful thinking? :)





From: David Anderson 
Sent: Sunday, November 5, 2017 4:53:53 PM
To: Juha Sointusalo; Jacob Klein
Cc: Rom Walton; BOINC Developers Mailing List; Boinc Projects; BOINC Alpha
Subject: Re: [boinc_dev] BOINC - October 2017 VirtualBox and VBoxWrapper updates



I rebuilt everything and uploaded it (same .zip filename).
The .exe size didn't change, but diff says it's different.
-- David

On 11/5/2017 12:09 PM, Juha Sointusalo wrote:

On 5 November 2017 at 11:14, Jacob Klein 
> wrote:

David / Juha / Rom:



I have concluded my testing (took about 6 hours), and 26200 has some serious 
problems!



There seems to be something wrong in the vboxwrapper David built. I can 
reproduce the problems with it.



I re-built vboxwrapper myself, with VS2010 and VS2013 to see if it's something 
with VS version. Neither had problems with my test app. Now I have ATLAS and 
Theory task running with vboxwrapper built with VS2013 and the tasks seem to be 
working fine, or at least started fine.



Jacob, here's something for you to test: 
https://drive.google.com/open?id=13naXH8_mPg3b4kVrvRLPUfw2yY6cGnaW . Version 
numbers are off, don't worry about them.



-Juha




___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_projects] BOINC - October 2017 VirtualBox and VBoxWrapper updates

2017-11-06 Thread Juha Sointusalo
On 6 November 2017 at 10:17, Laurence  wrote:

> Hi Jacob,
> On 05/11/17 10:14, Jacob Klein wrote:
>
> David / Juha / Rom:
>
> I have concluded my testing (took about 6 hours), and 26200 has some serious 
> problems!
>
> Attached is a .zip of my full results, across my testing with LHC@Home and 
> RNA World. It includes a results summary, results detail files of stderr.txt 
> logs, and the app_info.xml files I used.
>
> You don't need to test on LHC@home as are building our own vboxwrapper
> while we are waiting for PR 1946
>  to be merged.
>

The reason I tested on LHC is that I wanted to test on real world apps, LHC
has real world apps and I have already signed up there. That's all. Maybe
LHC-dev would have been better choice or maybe I should have asked you for
permission first but at that time the risk of VirtualBox 5.2 acting bad and
tasks returning bad science results seemed low enough.

I haven't run CMS or LHCb tasks for a while and I think the VM images and
job scripts were outdated so I had to test with ATLAS and Theory only.
There's a few completed tasks now and no sign of problems so far.

-Juha
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_projects] BOINC - October 2017 VirtualBox and VBoxWrapper updates

2017-11-06 Thread Laurence

Hi Jacob,


I am not a fan of using the word hacked. It suggests corners are being 
cut. We are trying to do things correctly. The modified code is in a 
fork and the changes were provided as a PR over 4 months ago. We used 
our dev and prod projects to test the changes and have been running this 
way while we wait for the changes to be included upstream. Until these 
changes are included upstream, we will be using the fork.



Cheers,


Laurence





On 06/11/17 14:52, Jacob Klein wrote:

Hi Laurence,

2 things.

1) I usually only do RNA World tasks (which rarely have VMs 
available), and set No New Tasks for any other VM project (because I 
want to give the RNA World monster task the best chance to complete 
successfully). But here, I needed a simple way to get new VM tasks, to 
test the new vboxwrapper. So, yes, I do need some VM project to test 
with, and I chose LHC. If you can think of a better one to test with, 
let me know.


2) Are you arguing semantics? If an app isn't using an official 
version of the vboxwrapper for an app, then it is using a hacked 
version. ie: The user has no idea what could be in that executable. If 
you are really making fixes to the codebase, then you should please 
consider making sure those fixes land in the official codebase! 
Development may be skeleton on it currently, but we are obviously 
still doing releases. And if your changes are in the codebase already, 
then you might be able to switch to using official 26200 soon.


My research indicates that 2 of the 4 projects I tested with, are 
indeed currently using hacked versions.


Official 26198 x64: vboxwrapper_26198_windows_x86_64.exe --- Size: 
1,375,232

LHCb version: vboxwrapper_26198ab7_windows_x86_64.exe --- Size: 1,696,768
Theory version: vboxwrapper_26198ab5_windows_x86_64.exe --- Size: 
1,695,744


Kind Regards,
Jacob




*From:* Laurence 
*Sent:* Monday, November 6, 2017 3:17 AM
*To:* Jacob Klein; David Anderson; Juha Sointusalo; Rom Walton
*Cc:* BOINC Developers Mailing List; Boinc Projects; BOINC Alpha
*Subject:* Re: [boinc_projects] [boinc_dev] BOINC - October 2017 
VirtualBox and VBoxWrapper updates


Hi Jacob,

On 05/11/17 10:14, Jacob Klein wrote:

David / Juha / Rom:

I have concluded my testing (took about 6 hours), and 26200 has some serious 
problems!

Attached is a .zip of my full results, across my testing with LHC@Home and RNA 
World. It includes a results summary, results detail files of stderr.txt logs, 
and the app_info.xml files I used.
You don't need to test on LHC@home as are building our own vboxwrapper 
while we are waiting for PR 1946 
 to be merged.

A summary of the issues is below. Please let me know when you think you have 
these issues fixed, and when there is a newer version for me to test!

Thanks,
Jacob

The main issues with 26200 are:

- (Major) The version number written to stderr.txt is incorrect! I believe it reads the 
file info, and for 26200, is printing: "vboxwrapper (7.9.26197)". This needs to 
be fixed, it is very confusing when testing/debugging!

- (Major) For all 4 of the LHC@Home VM projects, when trying to start a new 
task using 26200 using VirtualBox v5.2.x, you immediately get Computation Error.
...
stderr.txt says:
2017-11-05 03:20:47 (12552): Error 0x80bb0001 in vbox52::VBOX_VM::create_vm 
(c:\users\david\documents\boinc_git\boinc\samples\vboxwrapper\vbox_mscom_impl.cpp:835)
2017-11-05 03:20:47 (12552): Error Source : SessionMachine
2017-11-05 03:20:47 (12552): Error Description: This machine does not have any 
snapshots
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc005) at address 0x7FFAEAC4AB7F read 
attempt to address 0x0018

- (Major) For RNA World, when trying to restore a task using 26200 using 
VirtualBox v5.2.x (which I attempted using a copy of my data while offline!).. 
it fails to restore properly! :(
...
stderr.txt says:
2017-11-05 01:37:51 (14600): Restore from previously saved snapshot.
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc005) at address 0x7FFAEA5E8246 write 
attempt to address 0xE860

- (Minor) For LHCb and Theory, when trying to start a new task using 26200 
using VirtualBox v5.1.x, they will eventually fail mid-run. I'm not entirely 
sure, but this might be because they use a hacked VBoxWrapper for these 2 apps, 
and a 'standard' VBoxWrapper just won't work.
We haven't "/hacked/" the vboxwrapper, we spent 2 months debugging it! 
The issues you hit is that port 9618 is blocked for out going traffic 
on your machine.


http://lhcathome.web.cern.ch/test4theory/my-firewall-complaining-which-ports-does-project-use

Cheers,

Laurence




___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu

Re: [boinc_dev] [boinc_projects] BOINC - October 2017 VirtualBox and VBoxWrapper updates

2017-11-06 Thread Jacob Klein
Hi Laurence,

2 things.

1) I usually only do RNA World tasks (which rarely have VMs available), and set 
No New Tasks for any other VM project (because I want to give the RNA World 
monster task the best chance to complete successfully). But here, I needed a 
simple way to get new VM tasks, to test the new vboxwrapper. So, yes, I do need 
some VM project to test with, and I chose LHC. If you can think of a better one 
to test with, let me know.

2) Are you arguing semantics? If an app isn't using an official version of the 
vboxwrapper for an app, then it is using a hacked version. ie: The user has no 
idea what could be in that executable. If you are really making fixes to the 
codebase, then you should please consider making sure those fixes land in the 
official codebase! Development may be skeleton on it currently, but we are 
obviously still doing releases. And if your changes are in the codebase 
already, then you might be able to switch to using official 26200 soon.

My research indicates that 2 of the 4 projects I tested with, are indeed 
currently using hacked versions.

Official 26198 x64: vboxwrapper_26198_windows_x86_64.exe --- Size: 1,375,232
LHCb version: vboxwrapper_26198ab7_windows_x86_64.exe --- Size: 1,696,768
Theory version: vboxwrapper_26198ab5_windows_x86_64.exe --- Size: 1,695,744

Kind Regards,
Jacob




From: Laurence 
Sent: Monday, November 6, 2017 3:17 AM
To: Jacob Klein; David Anderson; Juha Sointusalo; Rom Walton
Cc: BOINC Developers Mailing List; Boinc Projects; BOINC Alpha
Subject: Re: [boinc_projects] [boinc_dev] BOINC - October 2017 VirtualBox and 
VBoxWrapper updates


Hi Jacob,

On 05/11/17 10:14, Jacob Klein wrote:

David / Juha / Rom:

I have concluded my testing (took about 6 hours), and 26200 has some serious 
problems!

Attached is a .zip of my full results, across my testing with LHC@Home and RNA 
World. It includes a results summary, results detail files of stderr.txt logs, 
and the app_info.xml files I used.

You don't need to test on LHC@home as are building our own vboxwrapper while we 
are waiting for PR 1946 to be merged.

A summary of the issues is below. Please let me know when you think you have 
these issues fixed, and when there is a newer version for me to test!

Thanks,
Jacob

The main issues with 26200 are:

- (Major) The version number written to stderr.txt is incorrect! I believe it 
reads the file info, and for 26200, is printing: "vboxwrapper (7.9.26197)". 
This needs to be fixed, it is very confusing when testing/debugging!

- (Major) For all 4 of the LHC@Home VM projects, when trying to start a new 
task using 26200 using VirtualBox v5.2.x, you immediately get Computation Error.
...
stderr.txt says:
2017-11-05 03:20:47 (12552): Error 0x80bb0001 in vbox52::VBOX_VM::create_vm 
(c:\users\david\documents\boinc_git\boinc\samples\vboxwrapper\vbox_mscom_impl.cpp:835)
2017-11-05 03:20:47 (12552): Error Source : SessionMachine
2017-11-05 03:20:47 (12552): Error Description: This machine does not have any 
snapshots
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc005) at address 0x7FFAEAC4AB7F read 
attempt to address 0x0018

- (Major) For RNA World, when trying to restore a task using 26200 using 
VirtualBox v5.2.x (which I attempted using a copy of my data while offline!).. 
it fails to restore properly! :(
...
stderr.txt says:
2017-11-05 01:37:51 (14600): Restore from previously saved snapshot.
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc005) at address 0x7FFAEA5E8246 write 
attempt to address 0xE860

- (Minor) For LHCb and Theory, when trying to start a new task using 26200 
using VirtualBox v5.1.x, they will eventually fail mid-run. I'm not entirely 
sure, but this might be because they use a hacked VBoxWrapper for these 2 apps, 
and a 'standard' VBoxWrapper just won't work.


We haven't "hacked" the vboxwrapper, we spent 2 months debugging it! The issues 
you hit is that port 9618 is blocked for out going traffic on your machine.

http://lhcathome.web.cern.ch/test4theory/my-firewall-complaining-which-ports-does-project-use

Cheers,

Laurence


___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


[boinc_dev] Transifex resource updates

2017-11-06 Thread Oliver Bock
Hi guys,

How or when are updated PO templates from locale/templates propagated to
Transifex? IIRC there was some automated bridge that was supposed to do
this periodically.

Thanks,
Oliver
___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.


Re: [boinc_dev] [boinc_projects] BOINC - October 2017 VirtualBox and VBoxWrapper updates

2017-11-06 Thread Laurence

Hi Jacob,

On 05/11/17 10:14, Jacob Klein wrote:

David / Juha / Rom:

I have concluded my testing (took about 6 hours), and 26200 has some serious 
problems!

Attached is a .zip of my full results, across my testing with LHC@Home and RNA 
World. It includes a results summary, results detail files of stderr.txt logs, 
and the app_info.xml files I used.
You don't need to test on LHC@home as are building our own vboxwrapper 
while we are waiting for PR 1946 
 to be merged.

A summary of the issues is below. Please let me know when you think you have 
these issues fixed, and when there is a newer version for me to test!

Thanks,
Jacob

The main issues with 26200 are:

- (Major) The version number written to stderr.txt is incorrect! I believe it reads the 
file info, and for 26200, is printing: "vboxwrapper (7.9.26197)". This needs to 
be fixed, it is very confusing when testing/debugging!

- (Major) For all 4 of the LHC@Home VM projects, when trying to start a new 
task using 26200 using VirtualBox v5.2.x, you immediately get Computation Error.
...
stderr.txt says:
2017-11-05 03:20:47 (12552): Error 0x80bb0001 in vbox52::VBOX_VM::create_vm 
(c:\users\david\documents\boinc_git\boinc\samples\vboxwrapper\vbox_mscom_impl.cpp:835)
2017-11-05 03:20:47 (12552): Error Source : SessionMachine
2017-11-05 03:20:47 (12552): Error Description: This machine does not have any 
snapshots
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc005) at address 0x7FFAEAC4AB7F read 
attempt to address 0x0018

- (Major) For RNA World, when trying to restore a task using 26200 using 
VirtualBox v5.2.x (which I attempted using a copy of my data while offline!).. 
it fails to restore properly! :(
...
stderr.txt says:
2017-11-05 01:37:51 (14600): Restore from previously saved snapshot.
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc005) at address 0x7FFAEA5E8246 write 
attempt to address 0xE860

- (Minor) For LHCb and Theory, when trying to start a new task using 26200 
using VirtualBox v5.1.x, they will eventually fail mid-run. I'm not entirely 
sure, but this might be because they use a hacked VBoxWrapper for these 2 apps, 
and a 'standard' VBoxWrapper just won't work.
We haven't "/hacked/" the vboxwrapper, we spent 2 months debugging it! 
The issues you hit is that port 9618 is blocked for out going traffic on 
your machine.


http://lhcathome.web.cern.ch/test4theory/my-firewall-complaining-which-ports-does-project-use

Cheers,

Laurence


___
boinc_dev mailing list
boinc_dev@ssl.berkeley.edu
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.