Processed: Re: Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2014-02-01 Thread Debian Bug Tracking System 
Processing control commands:

> tags -1 -unreproducible
Bug #690152 [src:bsaf] bsaf: FTBFS: Test 
org.jdesktop.application.TaskMonitorTest failed
Removed tag(s) unreproducible.

-- 
690152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2014-02-01 Thread Andreas Moog 
Control: tags -1 -unreproducible

On 01.02.2014 17:23, Andreas Beckmann wrote:
> On 2014-02-01 17:03, Niels Thykier wrote:
>>> Therefore removing the wheezy tag, as the new issue only affects sid.
> 
>> Is that "only sid" or "sid and jessie"?  You said the former, but the
>> bug is tagged "sid jessie" implying you might mean the other.
> 
> I don't know, haven't tried (and don't plan to). So read this as "not
> wheezy".

I can confirm that it also fails in testing, build log attached.
-- 
Andreas Moog, Berliner Str. 29, 36205 Sontra/Germany
PGP-encrypted mails preferred (Key-ID: 74DE6624)
PGP Fingerprint: 74CD D9FE 5BCB FE0D 13EE 8EEA 61F3 4426 74DE 6624


bsaf_1.9-3_amd64.build.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2014-02-01 Thread Andreas Beckmann 
On 2014-02-01 17:03, Niels Thykier wrote:
>> Therefore removing the wheezy tag, as the new issue only affects sid.

> Is that "only sid" or "sid and jessie"?  You said the former, but the
> bug is tagged "sid jessie" implying you might mean the other.

I don't know, haven't tried (and don't plan to). So read this as "not
wheezy".


Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2014-02-01 Thread Niels Thykier 
On 2014-02-01 16:39, Andreas Beckmann wrote:
> Control: tag -1 - wheezy
> 
> On Sunday, 10. March 2013 03:50:40 Andres Mejia wrote:
>> At this time, being this late into the release cycle, I would like to
>> support only the default-jdk. I am building with sbuild using a chroot
>> created by sbuild-createchroot as I believe this closely matches what
>> the buildd machines are running. The bsaf package builds and passes
> ...
>> I will be downgrading this bug to important as I don't believe
>> supporting cowbuilder, xvfb, or openjdk-7-jdk to be release critical.
> 
> On Saturday, 1. February 2014 14:59:57 Andreas Moog wrote:
>> the package fails to build when rebuilding with sbuild in a current sid
>> chroot, so I'm raising severity to "serious" again:
> 
> Therefore removing the wheezy tag, as the new issue only affects sid.
> 
> Andreas
> 
> [...]

Hi,

Is that "only sid" or "sid and jessie"?  You said the former, but the
bug is tagged "sid jessie" implying you might mean the other.

~Niels


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Re: Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2014-02-01 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 - wheezy
Bug #690152 [src:bsaf] bsaf: FTBFS: Test 
org.jdesktop.application.TaskMonitorTest failed
Removed tag(s) wheezy.

-- 
690152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2014-02-01 Thread Andreas Beckmann 
Control: tag -1 - wheezy

On Sunday, 10. March 2013 03:50:40 Andres Mejia wrote:
> At this time, being this late into the release cycle, I would like to
> support only the default-jdk. I am building with sbuild using a chroot
> created by sbuild-createchroot as I believe this closely matches what
> the buildd machines are running. The bsaf package builds and passes
...
> I will be downgrading this bug to important as I don't believe
> supporting cowbuilder, xvfb, or openjdk-7-jdk to be release critical.

On Saturday, 1. February 2014 14:59:57 Andreas Moog wrote:
> the package fails to build when rebuilding with sbuild in a current sid
> chroot, so I'm raising severity to "serious" again:

Therefore removing the wheezy tag, as the new issue only affects sid.

Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2013-03-09 Thread Andres Mejia 
On Sun, Mar 3, 2013 at 8:42 AM, gregor herrmann  wrote:
> On Sat, 02 Mar 2013 19:12:32 -0500, Andres Mejia wrote:
>
>> I just rebuilt bsaf on my machine that has the DISPLAY environment variable
>> set and
>
> In a chroot or in the "normal" environment?

The "normal" environment.

>> on a sid and wheezy chroot via sbuild-shell (which in turn uses
>> schroot) that does not have DISPLAY set. All builds succeeded and passed
>> the test suite.
>
> That's not surprising, since without DISPLAY the otherwise failing
> tests are skipped :)
>
> FWIW: The tests still fail for me in wheezy and sid cowbuilder amd64
> chroots, with DISPLAY set, with or without my earlier patch (to use
> xvfb).
>
> As mentioned earlier in this bug log by Matteo, building with
> openjdk-7-jdk works in the same setup.
>
> Cheers,
> gregor
>
> --
>  .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
>  : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
>  `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
>`-   NP: David Bowie: Suffragette City

At this time, being this late into the release cycle, I would like to
support only the default-jdk. I am building with sbuild using a chroot
created by sbuild-createchroot as I believe this closely matches what
the buildd machines are running. The bsaf package builds and passes
the test suite for me fine on my machine running Debian wheezy, inside
a wheezy chroot using sbuild, and inside a sid chroot using sbuild. My
machine has a display, the chroot environments do not have a display.

I will be downgrading this bug to important as I don't believe
supporting cowbuilder, xvfb, or openjdk-7-jdk to be release critical.
If someone else can reproduce the test case failure with the version
of bsaf in the archives as is, then feel free to raise it back,
otherwise fixing these other issues of supporting cowbuilder, xvfb,
and openjdk-7-jdk can wait.

-- 
~ Andres


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2013-03-06 Thread gregor herrmann 
On Sun, 03 Mar 2013 14:42:09 +0100, gregor herrmann wrote:

> As mentioned earlier in this bug log by Matteo, building with
> openjdk-7-jdk works in the same setup.

Not anymore:

[junit] Running org.jdesktop.application.TaskMonitorTest
[junit] Testsuite: org.jdesktop.application.TaskMonitorTest
[junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 0.429 sec
[junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 0.429 sec
[junit] 
[junit] Testcase: 
testMessageSucceeded(org.jdesktop.application.TaskMonitorTest):   FAILED
[junit] doInBackground
[junit] junit.framework.AssertionFailedError: doInBackground
[junit] at 
org.jdesktop.application.TaskMonitorTest.testMessageSucceeded(Unknown Source)
[junit] 
[junit] 

BUILD FAILED
/tmp/buildd/bsaf-1.9/build.xml:68: Test 
org.jdesktop.application.TaskMonitorTest failed


I'm attaching the debdiff I've been using ...
(also failed without xvfb).

Oh, and it works in a wheezy chroot. Now this is interesting ...


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Tracy Chapman: Cold Feet
diff -Nru bsaf-1.9/debian/changelog bsaf-1.9/debian/changelog
--- bsaf-1.9/debian/changelog	2011-07-14 00:21:31.0 +0200
+++ bsaf-1.9/debian/changelog	2013-03-06 22:12:23.0 +0100
@@ -1,3 +1,11 @@
+bsaf (1.9-3.1) UNRELEASED; urgency=low
+
+  * Non-maintainer upload.
+  * Fix "FTBFS: Test org.jdesktop.application.TaskMonitorTest failed"
+(Closes: #690152)
+
+ -- gregor herrmann   Wed, 06 Mar 2013 22:12:11 +0100
+
 bsaf (1.9-3) unstable; urgency=low
 
   * Team upload.
diff -Nru bsaf-1.9/debian/control bsaf-1.9/debian/control
--- bsaf-1.9/debian/control	2011-07-14 00:21:31.0 +0200
+++ bsaf-1.9/debian/control	2013-03-06 22:20:53.0 +0100
@@ -3,8 +3,8 @@
 Priority: optional
 Maintainer: Debian Java Maintainers 
 Uploaders: Andres Mejia , Andrew Ross 
-Build-Depends: debhelper (>= 7.0.50~), javahelper, default-jdk, ant,
- ant-optional, junit4, libnetx-java
+Build-Depends: debhelper (>= 7.0.50~), javahelper, openjdk-7-jdk, ant,
+ ant-optional, junit4, libnetx-java, xvfb, xauth
 Standards-Version: 3.9.2
 Homepage: http://kenai.com/projects/bsaf
 Vcs-Browser: http://git.debian.org/?p=pkg-java/bsaf.git
diff -Nru bsaf-1.9/debian/rules bsaf-1.9/debian/rules
--- bsaf-1.9/debian/rules	2011-07-14 00:21:31.0 +0200
+++ bsaf-1.9/debian/rules	2013-03-06 22:30:13.0 +0100
@@ -1,7 +1,12 @@
 #!/usr/bin/make -f
 
-export JAVA_HOME=/usr/lib/jvm/default-java
+include /usr/share/javahelper/java-vars.mk
+
+export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-$(JAVA_ARCH)
 export CLASSPATH=/usr/share/java/junit4.jar:/usr/share/java/netx.jar
 
 %:
 	dh $@ --with javahelper
+
+override_dh_auto_build:
+	xvfb-run -a dh_auto_build


signature.asc
Description: Digital signature

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2013-03-03 Thread gregor herrmann 
On Sat, 02 Mar 2013 19:12:32 -0500, Andres Mejia wrote:

> I just rebuilt bsaf on my machine that has the DISPLAY environment variable
> set and 

In a chroot or in the "normal" environment?

> on a sid and wheezy chroot via sbuild-shell (which in turn uses
> schroot) that does not have DISPLAY set. All builds succeeded and passed
> the test suite.

That's not surprising, since without DISPLAY the otherwise failing
tests are skipped :)
 
FWIW: The tests still fail for me in wheezy and sid cowbuilder amd64
chroots, with DISPLAY set, with or without my earlier patch (to use
xvfb).

As mentioned earlier in this bug log by Matteo, building with
openjdk-7-jdk works in the same setup.

Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: David Bowie: Suffragette City


signature.asc
Description: Digital signature

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2013-03-02 Thread Andres Mejia 
On Monday, January 7, 2013, Joost Yervante Damad wrote:

> On 01/07/2013 07:48 PM, gregor herrmann wrote:
>
>> On Sat, 15 Dec 2012 16:13:35 +0100, Joost Yervante Damad wrote:
>>
>>  I tried rebuilding the bsaf software in wheezy with default-jdk,
>>> which uses the openjdk from openjdk-6-jre-headless_6b24.
>>> It builds just fine.
>>> Is this really still an issue?
>>>
>>
>> It still fails to build for me in wheezy and sid chroots
>> - without my earlier patch because of
>>"Can't connect to X11 window server using ':0' as the value of the
>> DISPLAY variable."
>> - with the patch with the long java.beans stack trace
>>
>> I guess you had DISPLAY unset during the build and the problematic
>> tests were skipped?
>>
>
> Indeed, I did not have DISPLAY set. Unfortunately I forgot to keep a log
> of the build around.
>
> Joost
>
> __
> This is the maintainer address of Debian's Java team
>  pkg-java-maintainers>.
> Please use
> debian-j...@lists.debian.org for discussions and questions.
>

I just rebuilt bsaf on my machine that has the DISPLAY environment variable
set and on a sid and wheezy chroot via sbuild-shell (which in turn uses
schroot) that does not have DISPLAY set. All builds succeeded and passed
the test suite.

The chroot environment will not have DISPLAY set of course. In fact, there
should be a small number of environment variables set in an chroot
environment using schroot. My chroot environment has the following
variables set.

USER
HOME
XDG_SESSION_COOKIE
SCHROOT_CHROOT_NAME
SCHROOT_UID
LOGNAME
TERM
USERNAME
PATH
SCHROOT_COMMAND
SCHROOT_SESSION_ID
SCHROOT_ALIAS_NAME
SCHROOT_GROUP
SCHROOT_USER
SHELL
PWD
SCHROOT_GID

--
Andres


-- 
~ Andres

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2013-01-07 Thread Joost Yervante Damad 

On 01/07/2013 07:48 PM, gregor herrmann wrote:

On Sat, 15 Dec 2012 16:13:35 +0100, Joost Yervante Damad wrote:


I tried rebuilding the bsaf software in wheezy with default-jdk,
which uses the openjdk from openjdk-6-jre-headless_6b24.
It builds just fine.
Is this really still an issue?


It still fails to build for me in wheezy and sid chroots
- without my earlier patch because of
   "Can't connect to X11 window server using ':0' as the value of the DISPLAY 
variable."
- with the patch with the long java.beans stack trace

I guess you had DISPLAY unset during the build and the problematic
tests were skipped?


Indeed, I did not have DISPLAY set. Unfortunately I forgot to keep a log 
of the build around.


Joost


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2013-01-07 Thread gregor herrmann 
On Sat, 15 Dec 2012 16:13:35 +0100, Joost Yervante Damad wrote:

> I tried rebuilding the bsaf software in wheezy with default-jdk,
> which uses the openjdk from openjdk-6-jre-headless_6b24.
> It builds just fine.
> Is this really still an issue?

It still fails to build for me in wheezy and sid chroots
- without my earlier patch because of 
  "Can't connect to X11 window server using ':0' as the value of the DISPLAY 
variable."
- with the patch with the long java.beans stack trace

I guess you had DISPLAY unset during the build and the problematic
tests were skipped?


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: The Chieftains: The Parting of Friends-Kerry Fling


signature.asc
Description: Digital signature

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2012-12-15 Thread Joost Yervante Damad 

Hey,

I tried rebuilding the bsaf software in wheezy with default-jdk, which 
uses the openjdk from openjdk-6-jre-headless_6b24.


It builds just fine.

Is this really still an issue?

Joost


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: Bug #690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2012-11-23 Thread Michael Banck 
690152 fixed 1.9-3
thanks

On Wed, Oct 10, 2012 at 04:22:11PM +0200, Lucas Nussbaum wrote:
> Source: bsaf
> Version: 1.9-3
> Severity: serious
> Tags: wheezy sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20121010 qa-ftbfs
> Justification: FTBFS in wheezy on amd64
> 
> Hi,
> 
> During a rebuild of all packages in *wheezy*, your package failed to
> build on amd64.

I couldn't reproduce this on wheezy/amd64.  Please reopen if it still
FTBFS for you.


Cheers,

Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2012-11-04 Thread gregor herrmann 
On Sat, 03 Nov 2012 18:36:09 +, Matteo Vescovi wrote:

> The stack trace led me to suspect the root cause of the issue lies
> in the java.beans package.
> 
> I built the bsaf sources and tests with the default jdk
> (/usr/lib/jvm/default-java -> java-6-openjdk) and then ran the
> entire testsuite with openjdk-7-jdk by changing the exported
> JAVA_HOME to /usr/lib/jvm/java-7-openjdk-amd64
> 
> All tests passed with openjdk-7.

Cool, thanks for digging into this issue.

Does this mean this is actually an issue with openjdk-6 and the bugs
should be reassigned?

Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones: Honkey Tonk Woman


signature.asc
Description: Digital signature

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2012-11-03 Thread Matteo Vescovi 

Hi,

The stack trace led me to suspect the root cause of the issue lies in 
the java.beans package.


I built the bsaf sources and tests with the default jdk 
(/usr/lib/jvm/default-java -> java-6-openjdk) and then ran the entire 
testsuite with openjdk-7-jdk by changing the exported JAVA_HOME to 
/usr/lib/jvm/java-7-openjdk-amd64


All tests passed with openjdk-7.


Cheers,
- Matteo


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test, org.jdesktop.application.TaskMonitorTest, failed

2012-11-03 Thread Matteo Vescovi 
The first failing test is BadSessionStateTest. The first exception in 
the log is actually expected:


[junit] java.lang.ArrayIndexOutOfBoundsException: 0
[junit] 	  at 
com.sun.beans.ObjectHandler.dequeueResult(ObjectHandler.java:189)
[junit] 	  at 
java.beans.XMLDecoder.readObject(XMLDecoder.java:223)
[junit] 	  at 
org.jdesktop.application.LocalStorage.load(LocalStorage.java:197)
[junit] 	  at 
org.jdesktop.application.SessionStorage.restore(SessionStorage.java:381)

[junit]   at


This exception is the result of trying to load a malformed session file, 
which is expected to fail.



Further down the stack trace, there appears to be a hint on what is 
actually going wrong:



[junit] java.lang.reflect.InvocationTargetException
[junit] at java.awt.EventQueue.invokeAndWait(EventQueue.java:1068)
[junit] 	at 
javax.swing.SwingUtilities.invokeAndWait(SwingUtilities.java:1347)
[junit] 	at 
org.jdesktop.application.BadSessionStateTest.testBadSessionState(BadSessionStateTest.java:101)

[junit] Caused by: java.lang.StackOverflowError
[junit] at java.beans.Statement.invokeInternal(Statement.java:257)
[junit] at java.beans.Statement.access$000(Statement.java:56)
[junit] at java.beans.Statement$2.run(Statement.java:158)
[junit] at java.security.AccessController.doPrivileged(Native Method)
[junit] at java.beans.Statement.invoke(Statement.java:154)
[junit] at java.beans.Expression.getValue(Expression.java:115)
[junit] 	at 
java.beans.DefaultPersistenceDelegate.doProperty(DefaultPersistenceDelegate.java:227)
[junit] 	at 
java.beans.DefaultPersistenceDelegate.initBean(DefaultPersistenceDelegate.java:264)
[junit] 	at 
java.beans.DefaultPersistenceDelegate.initialize(DefaultPersistenceDelegate.java:408)
[junit] 	at 
java.beans.PersistenceDelegate.writeObject(PersistenceDelegate.java:116)

[junit] at java.beans.Encoder.writeObject(Encoder.java:74)


Cheers,
- Matteo


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test, org.jdesktop.application.TaskMonitorTest failed

2012-11-03 Thread Matteo Vescovi 

Hi,

Here's what I found out so far about this bug.

Unsetting the DISPLAY environment variable works around the FTBFS error 
by skipping the failing Junit tests. However, unsetting DISPLAY is not 
the preferable/acceptable solution, as it simply skips the failing tests.


Check out the build.xml. Several tests are only conditionally executed, 
depending on whether DISPLAY is set:


i.e.

if="have.display"/>


where property have.display is conditionally set earlier on based on:





I turned to debugging the Junit tests and determined that the following 
tests are failing:


 
 



Cheers,
- Matteo


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2012-11-03 Thread Ulrich Dangel 
* gregor herrmann wrote [24.10.12 17:13]:
Hi,

> Running the tests under xvfb I get a different failure:

JFTR I get the exact same error messages running it directly in X11.

> (and it goes on and on for pages)
> 
> So: no idea :/
> 
> (I'm still attaching the change to use xvfb which seems to be a good
> idea in any case.)
 
At least it looks like the behaviour with xvfb is consistent to a real
environment.

It works without a problem if no DISPLAY variable is set (as it just
doesn't run the tests).

cheers from the Dublin BSP,
Ulrich


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2012-10-24 Thread gregor herrmann 
On Thu, 11 Oct 2012 22:21:04 -0700, tony mancill wrote:

> >> During a rebuild of all packages in *wheezy*, your package failed to
> >> build on amd64.
> > I couldn't reproduce this in wheezy or sid, but I was only using pbuilder 
> > to test.
> I was able to get the build to fail by setting DISPLAY to something not
> accessible to the build machine, but it failed in the first unit test
> (different than the failure in the bug report).  After unsetting
> DISPLAY, the build is successful.  So I don't think it's the same issue.
>  My builds were in a cowbuilder chroot.

It fails for me in cowbuilder (without doing anything) in the first
unit test with a clear error message:

compile-test:
[javac] /tmp/buildd/bsaf-1.9/build.xml:49: warning: 'includeantruntime' was 
not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Compiling 26 source files to /tmp/buildd/bsaf-1.9/test
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
 [copy] Copying 28 files to /tmp/buildd/bsaf-1.9/test

check-display:

test:
[junit] Running org.jdesktop.application.AbstractBeanTest
[junit] Testsuite: org.jdesktop.application.AbstractBeanTest
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.046 sec
[junit] No protocol specified
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.046 sec
[junit] 
[junit] Testcase: fireOnEdtTest(org.jdesktop.application.AbstractBeanTest): 
Caused an ERROR
[junit] Can't connect to X11 window server using ':0' as the value of the 
DISPLAY variable.
[junit] java.lang.InternalError: Can't connect to X11 window server using 
':0' as the value of the DISPLAY variable.
[junit] at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
[junit] at 
sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:62)
[junit] at 
sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:178)
[junit] at java.security.AccessController.doPrivileged(Native Method)
[junit] at 
sun.awt.X11GraphicsEnvironment.(X11GraphicsEnvironment.java:142)
[junit] at java.lang.Class.forName0(Native Method)
[junit] at java.lang.Class.forName(Class.java:186)
[junit] at 
java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:82)
[junit] at sun.awt.X11.XToolkit.(XToolkit.java:112)
[junit] at java.lang.Class.forName0(Native Method)
[junit] at java.lang.Class.forName(Class.java:186)
[junit] at java.awt.Toolkit$2.run(Toolkit.java:849)
[junit] at java.security.AccessController.doPrivileged(Native Method)
[junit] at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:841)
[junit] at java.awt.Toolkit.getEventQueue(Toolkit.java:1698)
[junit] at java.awt.EventQueue.isDispatchThread(EventQueue.java:878)
[junit] at 
javax.swing.SwingUtilities.isEventDispatchThread(SwingUtilities.java:1360)
[junit] at 
javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(SwingPropertyChangeSupport.java:90)
[junit] at 
java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:229)
[junit] at 
org.jdesktop.application.AbstractBean.firePropertyChange(Unknown Source)
[junit] at 
org.jdesktop.application.AbstractBeanTest$TestBean.fire(Unknown Source)
[junit] at 
org.jdesktop.application.AbstractBeanTest.fireOnEdtTest(Unknown Source)
[junit] 
[junit] 

BUILD FAILED
/tmp/buildd/bsaf-1.9/build.xml:68: Test 
org.jdesktop.application.AbstractBeanTest failed


Running the tests under xvfb I get a different failure:
  
  (Side question: why are the tests run at dh_auto_build time and not
  under dh_auto_test?)

[junit] Running org.jdesktop.application.ApplicationTest
[junit] Testsuite: org.jdesktop.application.ApplicationTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.453 sec
[junit] Tests run: 8, Failures: 0, Errors: 0, Time elapsed: 0.453 sec
[junit] 
[junit] This test generates logger warnings.  Ignore them.
[junit] Running org.jdesktop.application.BadSessionStateTest
[junit] Testsuite: org.jdesktop.application.BadSessionStateTest
[junit] Oct 24, 2012 4:03:59 PM org.jdesktop.application.LocalStorage getId
[junit] WARNING: unspecified resource Application.id using 
BadSessionStateApplication
[junit] Oct 24, 2012 4:03:59 PM 
org.jdesktop.application.SingleFrameApplication initRootPaneContainer
[junit] WARNING: couldn't restore session [mainFrame.session.xml]
[junit] java.lang.ArrayIndexOutOfBoundsException: 0
[junit] at 
com.sun.beans.ObjectHandler.dequeueResult(ObjectHandler.java:189)
[junit] at java.beans.XMLDecoder.readObje

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2012-10-11 Thread tony mancill 
On 10/10/2012 07:12 PM, Miguel Landaeta wrote:
> On Wed, Oct 10, 2012 at 04:22:11PM +0200, Lucas Nussbaum wrote:
>> Source: bsaf
>> Version: 1.9-3
>> Severity: serious
>> Tags: wheezy sid
>> User: debian...@lists.debian.org
>> Usertags: qa-ftbfs-20121010 qa-ftbfs
>> Justification: FTBFS in wheezy on amd64
>>
>> Hi,
>>
>> During a rebuild of all packages in *wheezy*, your package failed to
>> build on amd64.
> 
> I couldn't reproduce this in wheezy or sid, but I was only using pbuilder to 
> test.

I was able to get the build to fail by setting DISPLAY to something not
accessible to the build machine, but it failed in the first unit test
(different than the failure in the bug report).  After unsetting
DISPLAY, the build is successful.  So I don't think it's the same issue.
 My builds were in a cowbuilder chroot.

tony




signature.asc
Description: OpenPGP digital signature

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2012-10-10 Thread Miguel Landaeta 
On Wed, Oct 10, 2012 at 04:22:11PM +0200, Lucas Nussbaum wrote:
> Source: bsaf
> Version: 1.9-3
> Severity: serious
> Tags: wheezy sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20121010 qa-ftbfs
> Justification: FTBFS in wheezy on amd64
> 
> Hi,
> 
> During a rebuild of all packages in *wheezy*, your package failed to
> build on amd64.

I couldn't reproduce this in wheezy or sid, but I was only using pbuilder to 
test.

-- 
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/
"Faith means not wanting to know what is true." -- Nietzsche


signature.asc
Description: Digital signature

Bug#690152: bsaf: FTBFS: Test org.jdesktop.application.TaskMonitorTest failed

2012-10-10 Thread Lucas Nussbaum 
Source: bsaf
Version: 1.9-3
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20121010 qa-ftbfs
Justification: FTBFS in wheezy on amd64

Hi,

During a rebuild of all packages in *wheezy*, your package failed to
build on amd64.

Relevant part:
>  debian/rules build
> dh build --with javahelper
>dh_testdir
>dh_auto_configure
>jh_linkjars
>dh_auto_build
> Buildfile: /«PKGBUILDDIR»/build.xml
> 
> init:
> [mkdir] Created dir: /«PKGBUILDDIR»/build
> [mkdir] Created dir: /«PKGBUILDDIR»/dist
> [mkdir] Created dir: /«PKGBUILDDIR»/test
> 
> compile:
> [javac] /«PKGBUILDDIR»/build.xml:37: warning: 'includeantruntime' was not 
> set, defaulting to build.sysclasspath=last; set to false for repeatable builds
> [javac] Compiling 38 source files to /«PKGBUILDDIR»/build
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
>  [copy] Copying 6 files to /«PKGBUILDDIR»/build
> 
> jar:
>   [jar] Building jar: /«PKGBUILDDIR»/dist/bsaf-1.9.jar
> 
> compile-test:
> [javac] /«PKGBUILDDIR»/build.xml:49: warning: 'includeantruntime' was not 
> set, defaulting to build.sysclasspath=last; set to false for repeatable builds
> [javac] Compiling 26 source files to /«PKGBUILDDIR»/test
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
>  [copy] Copying 28 files to /«PKGBUILDDIR»/test
> 
> check-display:
> 
> test:
> [junit] Running org.jdesktop.application.AbstractBeanTest
> [junit] Testsuite: org.jdesktop.application.AbstractBeanTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.044 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.044 sec
> [junit] 
> [junit] Running org.jdesktop.application.ApplicationActionMapTest
> [junit] Testsuite: org.jdesktop.application.ApplicationActionMapTest
> [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 0.17 sec
> [junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 0.17 sec
> [junit] 
> [junit] Running org.jdesktop.application.ApplicationDefaultLNFResourceTest
> [junit] Testsuite: 
> org.jdesktop.application.ApplicationDefaultLNFResourceTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.149 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.149 sec
> [junit] 
> [junit] Running org.jdesktop.application.ApplicationEndTest
> [junit] Testsuite: org.jdesktop.application.ApplicationEndTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.158 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.158 sec
> [junit] 
> [junit] Running org.jdesktop.application.ApplicationMotifLNFResourceTest
> [junit] Testsuite: 
> org.jdesktop.application.ApplicationMotifLNFResourceTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.149 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.149 sec
> [junit] 
> [junit] Running org.jdesktop.application.ApplicationNimbusLNFResourceTest
> [junit] Testsuite: 
> org.jdesktop.application.ApplicationNimbusLNFResourceTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.197 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.197 sec
> [junit] 
> [junit] Running org.jdesktop.application.ApplicationNoLNFResourceTest
> [junit] Testsuite: org.jdesktop.application.ApplicationNoLNFResourceTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.15 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.15 sec
> [junit] 
> [junit] Running org.jdesktop.application.ApplicationPrivateCtorTest
> [junit] Testsuite: org.jdesktop.application.ApplicationPrivateCtorTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.144 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.144 sec
> [junit] 
> [junit] Running org.jdesktop.application.ApplicationSystemLNFResourceTest
> [junit] Testsuite: 
> org.jdesktop.application.ApplicationSystemLNFResourceTest
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.158 sec
> [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.158 sec
> [junit] 
> [junit] Running org.jdesktop.application.LocalStorageTest
> [junit] Testsuite: org.jdesktop.application.LocalStorageTest
> [junit] Creating LocalStorage tmp directory 
> "/«PKGBUILDDIR»/build/local-storage.tmp"
> [junit] LocalStorage tmp directory: 
> "/«PKGBUILDDIR»/build/local-storage.tmp"
> [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.118 sec
> [junit] Tests run