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.
http://bertram.russia/hudson/job/jet-main/129/testReport/org.netbeans.test.cnd/CNDValidation/testCreateSampleProject/ Hello, our build is failing due to some error in CND. I just wonder how could that state happen in our repository - seems like some hudsons are not affected by this and some are. Thanks for looking at this asap, David
added to CC: Alexander Pepin - owner of CND tests could you please add to "Archive the artifacts" screenshots of failed tests (**/screen.png) and enable tests sometime screenshot can tell more than log CND tests very stable on deadlock for long time. it can be some configuration problem anyway - hard to say without screenshots
I have added there the "**/screen.png". I hope it is comma separated list. I will write back after we have one additional round. Right now we have one more failure so I will write here after we have the results for this again.
you can run commit validation tests without CND: ant commit-validation -Dvalidation.nb.cluster.cnd="" and than run only CND tests without checking results ant -f cnd.kit/build.xml -Dtest.config=commit it will not break build but we will have results
Ivan, this is not going to work. Unless we want to upset all people in development we have to disable the not 100% stable tests and stabilize them in private repositories without causing so much noise. I'd rather see you to disable failing tests or remove them from the commit validation until they are really stable. Can you please lead this? The less work for project teams, the better. Thanks. Btw. one option also is to use @RandomlyFails annotation and run our tests with ant -Dtest-unit-sys-prop.ignore.random.failures=true -Dtest-qa-functional-sys-prop.ignore.random.failures=true commit-validation in nbbuild/hudson/round-robin-push and individual builders. But it needs to be tested.
http://bertram.russia/hudson/job/jet-main/131/artifact/cnd.kit/build/test/qa-functional/work/o.n.t.c.C/csp/screen.png Can you please try to solve it either with Michal or with the CND team? Thanks.
It seems that this host is not configured properly to run CND tests. GNU compiler collection should be installed and path to it should be added to PATH environment variable. Anyway CND validation test should be adjusted to check the situation when compilers do not exist but the test will fail in that case either as build step will not be completed.
IMHO the error message from the CND tests should say something like "you need to have this and this installed on your machine to run these tests".
I will fix test
on Solaris machines /usr/sfw/bin should be added to PATH
fixed changeset 117831 3b9631f2679a please enable CND tests
I will enable CND tests only after I have confirmation from Michal Zlamal that our hudson machine bertram.russia has all the necessary things installed. Or do you access that machine and installed them there?
Plain invocation of "ant commit-validation" is used by all our developers and customers. We can assume they have java and ant somewhere, but we cannot assume they have gcc, application servers. Even in such situation the commit validation needs to succeed. Please keep that in mind and exclude all tests that have bigger requirements. Thanks.
2dstrupl: If you do not want to enable it - it is OK, if it will not affect only your job. I fixed test, so now it should pass even if gcc not found. I can fix PATH problem on bertram.russia as well as not gnome for vncserver, but let BE do it
Integrated into 'main-golden', will be available in build *200902220201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/3b9631f2679a User: Ivan Sidorkin <ivansidorkin@netbeans.org> Log: fixed #158796 Commit validation failure in CNDValidation
v/c