Re: Using Python/Tools/freeze to generate a compiled version of the harness

On 11/30/2009 09:42 PM, Bill Peck wrote:
>
> Hi Marian,
>
> I thought I'd mention that I stumbled across freeze for python.  It 
> allows you to compile python code into a native binary.
>
> python26 ../freeze/freeze.py -X PyDOC /usr/bin/beah-beaker-backend -m 
> encodings -m encodings.hex_codec -m encodings.ascii
>
> I had to add the encodings since freeze didn't figure it out 
> automatically.
>
> I also had to edit the config.c file that it generated.  It improperly 
> puts in a _warnings entry which is incorrect.
>
> After that I was able to compile the code with a simple make.
>
> [root <at> dell-pe1850-01 beah-beaker-backend]# eu-readelf -d 
> beah-beaker-backend |more
>
> Dynamic segment contains 29 entries:
>  Addr: 0x08390684  Offset: 0x348684  Link to section: [ 5] '.dynstr'
>   Type              Value
>   NEEDED            Shared library: [libpthread.so.0]
>   NEEDED            Shared library: [libdl.so.2]
>   NEEDED            Shared library: [libutil.so.1]
>   NEEDED            Shared library: [libm.so.6]
>   NEEDED            Shared library: [libc.so.6]
>   INIT              0x08057f58

Re: Using Python/Tools/freeze to generate a compiled version of the harness

On 12/01/2009 03:39 AM, Marian Csontos wrote:
> On 11/30/2009 09:42 PM, Bill Peck wrote:
>>
>> Hi Marian,
>>
>> I thought I'd mention that I stumbled across freeze for python.  It 
>> allows you to compile python code into a native binary.
>>
>> python26 ../freeze/freeze.py -X PyDOC /usr/bin/beah-beaker-backend -m 
>> encodings -m encodings.hex_codec -m encodings.ascii
>>
>> I had to add the encodings since freeze didn't figure it out 
>> automatically.
>>
>> I also had to edit the config.c file that it generated.  It 
>> improperly puts in a _warnings entry which is incorrect.
>>
>> After that I was able to compile the code with a simple make.
>>
>> [root <at> dell-pe1850-01 beah-beaker-backend]# eu-readelf -d 
>> beah-beaker-backend |more
>>
>> Dynamic segment contains 29 entries:
>>  Addr: 0x08390684  Offset: 0x348684  Link to section: [ 5] '.dynstr'
>>   Type              Value
>>   NEEDED            Shared library: [libpthread.so.0]
>>   NEEDED            Shared library: [libdl.so.2]
>>   NEEDED            Shared library: [libutil.so.1]
>>   NEEDED            Shared library: [libm.so.6]
>>   NEEDED            Shared library: [libc.so.6]

ReleaseAction SQL schema ?

Hi Bill,

I've merged the latest release-0.4 branch with my ticket543788 to do some testing to make sure everything
works as it should. The ReleaseAction class that you created though
is tripping up my environment here as I don't have the correct SQL system table schema. Do you have the SQL
alter commands that were used along with this code change?

Cheers
Raymond

System creator

Hi Bill,

I've changed some code on branch ticket541176 to enable the recording of the creator of systems in the
beaker inventory. I couldn't find anywhere else where we were recording this information so I added it in
myself. 
This has only been setup for when systems are being added via the GUI. I'm not really familiar with other
parts of the code where
systems are potentially being added. I imagine there at least a couple of other places in the codebase?

Also, is it at all possible to (reliably)find out and retrospectively add the creators to systems already
in existence (possibly looking through the earliest system history and look at who was credited with
first changing a systems attributes). Can you think of a reason this wouldn't work?

Cheers
Raymond

Re: ReleaseAction SQL schema ?

On 12/13/2009 04:51 PM, Raymond Mancy wrote:
> Hi Bill,
>
> I've merged the latest release-0.4 branch with my ticket543788 to do some testing to make sure everything
works as it should. The ReleaseAction class that you created though
> is tripping up my environment here as I don't have the correct SQL system table schema. Do you have the SQL
alter commands that were used along with this code change?
>
> Cheers
> Raymond
>    

Hi Raymond,

The following should fix it for you.

mysql>  alter table system add column reprovision_distro_id int(11);
mysql>  alter table system add column release_action_id int(11);

Then update remaining DB changes with

# beaker-init

git branches and master

Hi Raymond,

I'm thinking its time to bite the bullet and fix the git repo.  Right 
now we have release-0.4 branch where we have been putting fixes and some 
new development that you have been working on like new search.  Then we 
have master where Marian and I have been working on the scheduler 
version.  This is painful because we have to commit fixes to both 
release-0.4 and to master.  Its all my fault for not understanding git 
and how branches work in it. (hint - they actually work unlike cvs!).

So I'd like to make master the main branch and move all development into 
branches.  This way we can always commit bug fixes to master and push a 
new release out when needed but continue to develop in branches and when 
done merge into master.

I'm willing to merge release-0.4 into master, I'll disable all the 0.5 
schema changes by commenting them out.  Then I'll branch a scheduler 
version from that which will cleanly merge back in later.

Does this sound reasonable?  Will you be able to bring your new search 
and column view code to master? I'd like them to be a branch off of 
master so that we can then merge them in when we are done testing.

If we get this straightened out then it will be much easier to develop 
and fix bugs.

beah and multi-host

Hi Marian,

I kicked off a multihost job and its giving the following output on the 
console...

12/14/09 13:12:25  testID:408 finish:
                                       12/14/09 13:12:35  JobID:109 
Test:/kernel/filesystems/nfs/connectathon-mh Response:1
                      12/14/09 13:12:35  testID:409 start:

rhts-sync-block Timeout!
                                                                                  rhts-sync-block Timeout!
     rhts-sync-block Timeout!
                             rhts-sync-block Timeout!
                                                     rhts-sync-block 
Timeout!
                                                                             rhts-sync-block Timeout!

I'll attach the xml I used to submit the job.  feel free to add a 
reserve task on the end so you can debug.

Re: beah and multi-host

Re: beah and multi-host

On 12/14/2009 01:28 PM, Bill Peck wrote:

On 12/14/2009 01:17 PM, Bill Peck wrote:

Hi Marian,

I kicked off a multihost job and its giving the following output on the console...

12/14/09 13:12:25  testID:408 finish:
                                      12/14/09 13:12:35  JobID:109 Test:/kernel/filesystems/nfs/connectathon-mh Response:1
                     12/14/09 13:12:35  testID:409 start:
                                                         rhts-sync-block Timeout!
                                                                                 rhts-sync-block Timeout!
    rhts-sync-block Timeout!
                            rhts-sync-block Timeout!
                                                    rhts-sync-block Timeout!
                                                                            rhts-sync-block Timeout!

Hold off on investigating that..  I forgot to update the dependencies so that it would pull in the right packages on RHEL3.  Grrr...

Ok,  straightened out the harness package for rhel3, now I'm at both client and server being blocked.  Can you look into what could be wrong?  my job will probably abort pretty soon..  if it does you can submit it again with the xml I gave you.

Thanks!

 

I'll attach the xml I used to submit the job.  feel free to add a reserve task on the end so you can debug.


_______________________________________________ Beaker-devel mailing list Beaker-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/beaker-devel

_______________________________________________ Beaker-devel mailing list Beaker-devel <at> lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/beaker-devel

Re: git branches and master

----- "Bill Peck" <bpeck <at> redhat.com> wrote:

> From: "Bill Peck" <bpeck <at> redhat.com>
> To: "List for the development of the Beaker project" <beaker-devel <at> lists.fedorahosted.org>,
"Raymond Mancy"
> <rmancy <at> redhat.com>, "Marian Csontos" <mcsontos <at> redhat.com>
> Sent: Tuesday, December 15, 2009 1:16:48 AM GMT +10:00 Brisbane
> Subject: git branches and master
>
> Hi Raymond,
> 
> I'm thinking its time to bite the bullet and fix the git repo.  Right
> 
> now we have release-0.4 branch where we have been putting fixes and
> some 
> new development that you have been working on like new search.  Then
> we 
> have master where Marian and I have been working on the scheduler 
> version.  This is painful because we have to commit fixes to both 
> release-0.4 and to master.  Its all my fault for not understanding git
> 
> and how branches work in it. (hint - they actually work unlike cvs!).
> 
> So I'd like to make master the main branch and move all development
> into 
> branches.  This way we can always commit bug fixes to master and push
> a 
> new release out when needed but continue to develop in branches and
> when 
> done merge into master.

Sure. This makes sense. Once you have merged release-0.4 into master I'll
create all new devel branches to track master.

> 
> I'm willing to merge release-0.4 into master, I'll disable all the 0.5
> 
> schema changes by commenting them out.  Then I'll branch a scheduler 
> version from that which will cleanly merge back in later.
> 
> Does this sound reasonable? 

Yep.

> Will you be able to bring your new search
> 
> and column view code to master? I'd like them to be a branch off of 
> master so that we can then merge them in when we are done testing.
>
They're currently sitting in their own branch, so once the testing is done it should
be able to be merged easily enough with master.

> If we get this straightened out then it will be much easier to develop
> 
> and fix bugs.

Raymond