This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 110820 - mobility8/emulators-inst/wtk22_linux.zip spuriously added to build
Summary: mobility8/emulators-inst/wtk22_linux.zip spuriously added to build
Status: CLOSED FIXED
Alias: None
Product: qa
Classification: Unclassified
Component: Tests (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@mobility
URL: http://deadlock.netbeans.org/hudson/j...
Keywords: ARCH, T9Y
Depends on:
Blocks: 111946
  Show dependency tree
 
Reported: 2007-07-24 18:57 UTC by Jesse Glick
Modified: 2011-06-10 09:15 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2007-07-24 18:57:12 UTC
See URL for an example.

It seems that mobility/project/test/build-qa-functional.xml#prepare-wtk modifies the content of the build. This is
unacceptable for a test. You should instead find some way to make the runtime code optionally look for emulators in a
different directory, and pass this directory in from the test.
Comment 1 Lukas Hasik 2007-07-25 08:50:21 UTC
I don't see anything wrong in this  behavior of tests. We do our best to create a enviroment that mimics real world.

When you *install* a build with mobility then there will be the mobility8/emulators-inst/wtk22_[linux|win].zip  
During the first start of the IDE the wtk.zip is unzipped to user's directory. The platform is also registered to be
available in IDE.

closing as INVALID.

Comment 2 Jesse Glick 2007-07-25 16:56:04 UTC
I have to say I really disagree with this behavior. Anything present in the build installation should come from a proper
NBM, and tests should never modify the contents of the build. The concrete problem I have noticed so far is that golden
file generation is messed up by this (i.e. the result varies depending on whether mobility tests were run or not), which
I can work around but would prefer a clean fix:

Checking in nbbuild/build.xml;
/shared/data/ccvs/repository/nbbuild/build.xml,v  <--  build.xml
new revision: 1.820; previous revision: 1.819
done

Packaging of IDE ZIP files from builders is quite possibly broken by this as well, but I have not investigated so far.
Comment 3 Jiri Skrivanek 2007-07-30 11:00:34 UTC
I fixed it by moving tests to the end of build cycle:

http://nbbuild.netbeans.org/source/browse/nbbuild/hudson/trunk?r1=1.48&r2=1.49
Comment 4 Jesse Glick 2007-07-30 17:34:55 UTC
I don't think moving tests to the end of the cycle will really change anything, except to make any resulting problems
less deterministic, since the installed file will be left in place for the next incremental build, in case this one
passes. One workaround would be to explicitly delete matching files right after running tests; either (1) the build
fails before getting to tests, (2) the tests run and the file is deleted, or (3) the build aborts during the tests, in
which case the file is left behind but the next build will be a clean build anyway.
Comment 5 Jesse Glick 2007-08-10 22:04:00 UTC
I have put in the workaround of explicitly deleting these files after tests complete.
Comment 6 Jiri Skrivanek 2007-08-13 15:56:42 UTC
Fixed - wtk is removed after tests finishes.

/cvs/mobility/project/test/build-qa-functional.xml,v  <--  build-qa-functional.xml
new revision: 1.5; previous revision: 1.4

/cvs/nbbuild/hudson/trunk,v  <--  trunk
new revision: 1.59; previous revision: 1.58
Comment 7 Jesse Glick 2007-08-13 19:41:52 UTC
x
Comment 8 Jesse Glick 2007-08-13 19:43:51 UTC
OK. BTW I still wanted to delete testtools/ so resurrecting that part of the line you deleted in the trunk script.
(trunk 1.60)
Comment 9 Jiri Skrivanek 2007-08-15 11:07:10 UTC
OK.