Hi Petr,
Hmm, quite many of the errors are caused by the test
qatesttool/framework/basic/f_basic_protected_libraries.bas. It is broken. It
leaves the user configuration user/basic in an inconsistent state.
Thank you for the hint. The test is being actively maintained but i was not aware of any serious problems with it.
However, i will investigate and modify the test so it will not leave the office in an undefined state.
Also the test qatesttool/framework/basic/f_scripting_addpkg.bas made us some
problems. OOo crashes when you try to add the
qatesttool/framework/basic/input/pkgmgr/capitalise.uno.pkg and you use
gcj/gij as JRE.
This is quite probable as i do not do any testing on GCJ. In order to cover as much code as possible i use the Sun Java
exclusively. For now i do not know the status of our support for GCJ but we should definitely support it, i will check.
Both of the problems happen also with the upstream package. Both tests are not
used in qatesttool/script/unix/OOoTestRun_unix.sh. Is it because these are
known bugs?
Known bugs: Usually we try to track bugs in the issues by marking them as
warnlogs or qaerrorlogs.
We disable non-working tests by printing a warnlog and - if required - skipping
the entire testcase.
It might well be that the script (OOoTestRun_unix.sh) is out of sync or we fail
to update the tests within reasonable time.
I wonder if the scripts below qatesttool/script are uptodate and if you use
them as well.
Thanks in advance.
You're welcome. If you have more questions please feel free to ask.
Joerg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
