Bug in build tests

[Elton Alves]

Hi,

Thanks for your prompt reply to my last post.

I have another showstopper: cannot build the test suite in 6 out of 8 versions i tried, namely (bugIds=) 31460, 51322, 53981, 55341, 67774, 87376. 

below is a fragment of the log generated with "ant buildtests -DfixId=31460 -Dtag=pre-fix".

i appreciate your help,
Elton

===================================================================

     [exec] [ajbuild-zip] Building zip: /home/elton/tmp/repository_tests/ibugs_aspectj-1.3/versions/31460/pre-fix/org.aspectj/modules/aj-build/jars/ajbrowse\
r-all.jar
     [exec] BuildException zipping ajbrowserProblem creating zip: /home/elton/tmp/repository_tests/ibugs_aspectj-1.3/versions/31460/pre-fix/org.aspectj/modu\

les/aj-build/jars/testing-util.jar (No such file or directory)

     [exec] Problem creating zip: /home/elton/tmp/repository_tests/ibugs_aspectj-1.3/versions/31460/pre-fix/org.aspectj/modules/aj-build/jars/testing-util.j\

ar (No such file or directory)
     [exec]     at org.apache.tools.ant.taskdefs.Zip.execute(Zip.java:436)
     [exec]     at org.aspectj.internal.tools.ant.taskdefs.AntBuilder.executeTask(AntBuilder.java:489)
     [exec]     at org.aspectj.internal.tools.ant.taskdefs.AntBuilder.assembleAll(AntBuilder.java:466)
     [exec]     at org.aspectj.internal.tools.build.Builder.buildAll(Builder.java:268)
     [exec]     at org.aspectj.internal.tools.build.Builder.build(Builder.java:198)
     [exec]     at org.aspectj.internal.tools.ant.taskdefs.BuildModule.build(BuildModule.java:142)

     [exec]     at org.aspectj.internal.tools.ant.taskdefs.BuildModule.execute(BuildModule.java:116)
     [exec]     at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:166)
     [exec]     at org.apache.tools.ant.Task.perform(Task.java:319)
     [exec]     at org.apache.tools.ant.Target.execute(Target.java:309)
     [exec]     at org.apache.tools.ant.Target.performTasks(Target.java:336)
     [exec]     at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
     [exec]     at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:371)
     [exec]     at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:143)
     [exec]     at org.apache.tools.ant.Task.perform(Task.java:319)
     [exec]     at org.apache.tools.ant.Target.execute(Target.java:309)
     [exec]     at org.apache.tools.ant.Target.performTasks(Target.java:336)
     [exec]     at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
     [exec]     at org.apache.tools.ant.Project.executeTargets(Project.java:1250)
     [exec]     at org.apache.tools.ant.Main.runBuild(Main.java:610)
     [exec]     at org.apache.tools.ant.Main.start(Main.java:196)
     [exec]     at org.apache.tools.ant.Main.main(Main.java:235)
===================================================================

--
Elton Renan Magalhães Alves
Ciências da Computação - 2005.2
+55 81 87988689
+55 81 87316322

[Valentin Dallmeier]

Hi!

This looks strange. Please try the following for each bug:

ant cleanversion
ant buildversion
ant buildtests

For some bugs, it is necessary to first compile AspectJ. However, for
other bugs the test suite does not compile if you first build AspectJ.
These problems are due to the project history of AspectJ. I've fixed
as many of those as possible, but some still persist. Please get back
to me with the outcome of the above steps.

Regards,

Valentin

> --
> You received this message because you are subscribed to the Google Groups
> "iBugs" group.
> To post to this group, send email to ib...@googlegroups.com.
> To unsubscribe from this group, send email to
> ibugs+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/ibugs?hl=en.
>

[Elton Alves]

Hi Valentim,

i was doing this already: ant clean, ant buildversion and ant
buildtests (passing the corresponding parameters). the error occurs
in the buildtests step.

i was very surprised to note that when i run:

- ant clean
- ant buildversion
- ant buildversion (duplicated)
- ant buildtests

the build succeeds.
let me know if you have any guess.
Elton

On Jul 24, 5:27 am, Valentin Dallmeier <valentin.dallme...@gmail.com>
wrote:

> Hi!
>
> This looks strange. Please try the following for each bug:
>
> ant cleanversion
> ant buildversion
> ant buildtests
>
> For some bugs, it is necessary to first compile AspectJ. However, for
> other bugs the test suite does not compile if you first build AspectJ.
> These problems are due to the project history of AspectJ. I've fixed
> as many of those as possible, but some still persist. Please get back
> to me with the outcome of the above steps.
>
> Regards,
>
> Valentin
>

[Valentin Dallmeier]

Mhh, I've never witnessed this behavior before. What system are you working on?

Valentin

26.07.2010 16:19 schrieb am "Elton Alves" <eltonren...@gmail.com>:

Hi Valentim,

i was doing this already: ant clean, ant buildversion and ant
buildtests (passing the corresponding parameters).   the error occurs
in the buildtests step.

i was very surprised to note that when i run:

- ant clean
- ant buildversion
- ant buildversion (duplicated)
- ant buildtests

the build succeeds.
let me know if you have any guess.
Elton

On Jul 24, 5:27 am, Valentin Dallmeier <valentin.dallme...@gmail.com>
wrote:

> Hi!
>
> This looks strange. Please try the following for each bug:
>
> ant cleanversion

> ant buil...

> On Fri, Jul 23, 2010 at 9:02 PM, Elton Alves <eltonrenan.al...@gmail.com> wrote:
> > Hi,
>

> > Tha...

--

You received this message because you are subscribed to the Google Groups "iBugs" group.

To post to ...

[Elton Alves]

Hi,
the system is Ubuntu (version 9.04 )

On Jul 26, 11:21 am, Valentin Dallmeier <valentin.dallme...@gmail.com>
wrote:

> Mhh, I've never witnessed this behavior before. What system are you working
> on?
>
> Valentin
>

[Francisco Servant]

I have also found that for some versions, you need to run
'buildversion' twice.
My guess is that this is a problem of the build process of AspectJ,
and that modules are being built in the wrong order.
I guess that the first compilation expects a module that has not built
yet and it stops. Then, the second compilation behaves differently,
because there are modules that have already been built by the first
one, and this time it succeeds.

I haven't checked the compilation scripts to confirm that this is
true, but it sounds reasonable :)

[Valentin Dallmeier]

I agree, this sounds reasonable. As mentioned before, I've tried to
remove as many of these problems as possible, but for some versions
the problem persists. One solution might be to hard code a double
build into build.xml.

Valentin