You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Lars Heill <La...@Sun.COM> on 2006/05/16 11:37:11 UTC

Snapshot build problem on trunk

Hi,

I run a daily clean snapshot build on derby trunk.

The last couple of days ant snapshot has failed, saying:

    BUILD FAILED
    /home/pakker/derby/code/build.xml:1559: /home/pakker/derby/code/jars/sane not found.

after successful runs of ant clobber, ant insane.

Could this be related to the change in r405563?

Thanks,
Lars

Re: Snapshot build problem on trunk

Posted by Andrew McIntyre <mc...@gmail.com>.
On 5/16/06, Rick Hillegas <Ri...@sun.com> wrote:
>
> Could there be some extra magic which
> http://wiki.apache.org/db-derby/DerbySnapshotOrRelease should document?
> When I follow the steps in (2), I get an error. Here are the steps:
>
>  </snip>
>
>   600  ant -quiet insane
>   601  ant -Dsane=false snapshot
>
> and here is the failure:
>
> BUILD FAILED
> C:\cygwin\home\rh161140\derby\mainline\trunk\build.xml:1546:
> C:\cygwin\home\rh161140\derby\mainline\trunk\jars\insane not found.

No magic. Works for me. The jars/insane dir should be created as a
part of the snapshot target by virtue of calling the buildjars target
while in insane mode. See build.xml:881.

andrew

Re: Snapshot build problem on trunk

Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi Andrew,

Could there be some extra magic which 
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease should document? 
When I follow the steps in (2), I get an error. Here are the steps:

  587  ant clobber
  588  ls
  589  rm -rf jars
  590  rm -rf javadoc
  591  rm -rf snapshot
  592  ls
  593  ant sane
  594  ant all
  595  ant -quiet buildjars
  596  ls jars
  597  ant -quiet clobber
  598  ls jars
  599  ls jars/sane
  600  ant -quiet insane
  601  ant -Dsane=false snapshot

and here is the failure:

BUILD FAILED
C:\cygwin\home\rh161140\derby\mainline\trunk\build.xml:1546: 
C:\cygwin\home\rh161140\derby\mainline\trunk\jars\insane not found.

Andrew McIntyre wrote:

> On 5/16/06, Lars Heill <La...@sun.com> wrote:
>
>> Hi,
>>
>> I run a daily clean snapshot build on derby trunk.
>>
>> The last couple of days ant snapshot has failed, saying:
>>
>>     BUILD FAILED
>>     /home/pakker/derby/code/build.xml:1559: 
>> /home/pakker/derby/code/jars/sane not found.
>>
>> after successful runs of ant clobber, ant insane.
>>
>> Could this be related to the change in r405563?
>
>
> Well, I guess I'm *not* the only person running the snapshot target. :-)
>
> Yes, it is now necessary to run a sane build before the snapshot
> target as well. See the instructions at
> http://wiki.apache.org/db-derby/DerbySnapshotOrRelease
>
> I suppose the part which zips up the debug-lib target could be broken
> out and made conditional on the sane jars being available, but the
> intended purpose of the snapshot target  is to assist committers in
> producing snapshots to put up on the Derby website. As such, I'd like
> to make sure that the debug-lib snapshots are posted whenever the
> snapshots are updated on the site. Failing to complete the snapshot
> target because the sane jars are not available is the right thing to
> do here.
>
> If it's being used for other purposes, then I'm sure we can find a
> compromise. Perhaps a new target that just builds the non-debug
> version of the snapshot?
>
> andrew



Re: Snapshot build problem on trunk

Posted by Lars Heill <La...@Sun.COM>.

Andrew McIntyre wrote, On 05/17/06 01:37:
> On 5/16/06, Lars Heill <La...@sun.com> wrote:
>> Hi,
>>
>> I run a daily clean snapshot build on derby trunk.
>>
>> The last couple of days ant snapshot has failed, saying:
>>
>>     BUILD FAILED
>>     /home/pakker/derby/code/build.xml:1559: 
>> /home/pakker/derby/code/jars/sane not found.
>>
>> after successful runs of ant clobber, ant insane.
>>
>> Could this be related to the change in r405563?
> 
> Well, I guess I'm *not* the only person running the snapshot target. :-)
> 
> Yes, it is now necessary to run a sane build before the snapshot
> target as well. See the instructions at
> http://wiki.apache.org/db-derby/DerbySnapshotOrRelease
> 
> I suppose the part which zips up the debug-lib target could be broken
> out and made conditional on the sane jars being available, but the
> intended purpose of the snapshot target  is to assist committers in
> producing snapshots to put up on the Derby website. As such, I'd like
> to make sure that the debug-lib snapshots are posted whenever the
> snapshots are updated on the site. Failing to complete the snapshot
> target because the sane jars are not available is the right thing to
> do here.
> 
> If it's being used for other purposes, then I'm sure we can find a
> compromise. Perhaps a new target that just builds the non-debug
> version of the snapshot?

Thanks!  Back in business :)

I do this exercise for a "release test" scenario: what would the
quality be if the current head of trunk was final release code.
As such, I have no need for the debug bits. 
But hey, the extra 2 minutes is acceptable... ;)

Cheers,
Lars

Re: Snapshot build problem on trunk

Posted by Andrew McIntyre <mc...@gmail.com>.
On 5/16/06, Lars Heill <La...@sun.com> wrote:
> Hi,
>
> I run a daily clean snapshot build on derby trunk.
>
> The last couple of days ant snapshot has failed, saying:
>
>     BUILD FAILED
>     /home/pakker/derby/code/build.xml:1559: /home/pakker/derby/code/jars/sane not found.
>
> after successful runs of ant clobber, ant insane.
>
> Could this be related to the change in r405563?

Well, I guess I'm *not* the only person running the snapshot target. :-)

Yes, it is now necessary to run a sane build before the snapshot
target as well. See the instructions at
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

I suppose the part which zips up the debug-lib target could be broken
out and made conditional on the sane jars being available, but the
intended purpose of the snapshot target  is to assist committers in
producing snapshots to put up on the Derby website. As such, I'd like
to make sure that the debug-lib snapshots are posted whenever the
snapshots are updated on the site. Failing to complete the snapshot
target because the sane jars are not available is the right thing to
do here.

If it's being used for other purposes, then I'm sure we can find a
compromise. Perhaps a new target that just builds the non-debug
version of the snapshot?

andrew