run.dbsq:
--
run.typerel:
--
run.bridge:
--
[java] FAILURES!!!
[java] Tests run: 253, Failures: 3, Errors: 0
--
run.bridge.rmmci:
--
[java] FAILURES!!!
[java] Tests run: 253, Failures: 3, Errors: 0
--
run.util:
[java]
--
run.clustering:
--
run.dbsq:
--
run.typerel:
--
run.bridge:
--
[java] FAILURES!!!
[java] Tests run: 253, Failures: 17, Errors: 0
--
run.bridge.rmmci:
--
[java] FAILURES!!!
[java] Tests run: 253, Failures: 17, Errors: 0
--
run.util:
[java]
--
run.clustering:
--
run.dbsq:
--
run.typerel:
--
run.bridge:
--
[java] FAILURES!!!
[java] Tests run: 253, Failures: 17, Errors: 0
--
run.bridge.rmmci:
--
[java] FAILURES!!!
[java] Tests run: 253, Failures: 17, Errors: 0
--
run.util:
[java]
--
run.clustering:
--
Nightly build user wrote:
run.dbsq:
--
[java] FAILURES!!!
[java] Tests run: 192, Failures: 1, Errors: 0
--
I think the failures of yesterday and the day before were related to the
fact that they took 19 hours, which may be related to recent changes on the
server. I'm glad that
run.dbsq:
--
[java] FAILURES!!!
[java] Tests run: 192, Failures: 1, Errors: 0
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
run.util:
[java]
--
run.clustering:
--
run.releasestrategy:
--
run.all:
___
Developers
run.dbsq:
--
[java] FAILURES!!!
[java] Tests run: 192, Failures: 1, Errors: 0
--
run.typerel:
--
run.bridge:
--
[java] FAILURES!!!
[java] Tests run: 253, Failures: 0, Errors: 11
--
run.bridge.rmmci:
--
[java] FAILURES!!!
[java] Tests run: 253, Failures: 0,
run.dbsq:
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
run.util:
[java] ...F.
--
[java] FAILURES!!!
[java] Tests run: 8, Failures: 1, Errors: 0
--
run.clustering:
--
run.releasestrategy:
--
run.all:
___
Developers
FYI,
Nightly build user wrote:
run.bridge.rmmci:
--
[java] FAILURES!!!
[java] Tests run: 253, Failures: 0, Errors: 1
This had to do with a Cloud parameter of a 'Function'. Parameters must
be serializable, certainly when using RMMCI. RemoteCloud is not
serializable.
run.dbsq:
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
[java] FAILURES!!!
[java] Tests run: 253, Failures: 0, Errors: 1
--
run.util:
[java]
--
run.clustering:
--
run.releasestrategy:
--
run.all:
___
Developers
Nightly build user wrote:
run.bridge.rmmci:
--
[java] FAILURES!!!
[java] Tests run: 251, Failures: 1, Errors: 0
..
run.clustering:
So the clustering test-cases indeed succeed now, as I predicted.
Sadly this did not yet result in dissappearance of the message, becausw
now
Nightly build user wrote:
run.clustering:
--
[java] FAILURES!!!
[java] Tests run: 9, Failures: 4, Errors: 0
I think the firewall on cvs.mmbase.org has now been correctly adapted. I predict
no test-case errors tonight.
Michiel
--
Michiel Meeuwissen mihxil'
run.dbsq:
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
[java] FAILURES!!!
[java] Tests run: 251, Failures: 1, Errors: 0
--
run.util:
[java]
--
run.clustering:
--
run.releasestrategy:
--
run.all:
___
Developers
run.dbsq:
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
run.util:
[java]
--
run.clustering:
--
[java] FAILURES!!!
[java] Tests run: 9, Failures: 4, Errors: 0
--
run.releasestrategy:
--
run.all:
___
Developers
run.dbsq:
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
run.util:
[java]
--
run.clustering:
--
[java] FAILURES!!!
[java] Tests run: 9, Failures: 4, Errors: 0
--
run.releasestrategy:
--
run.all:
___
Developers
run.dbsq:
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
run.util:
[java]
--
run.clustering:
--
[java] FAILURES!!!
[java] Tests run: 9, Failures: 4, Errors: 0
--
run.releasestrategy:
--
run.all:
___
Developers
run.dbsq:
--
[java] FAILURES!!!
[java] Tests run: 192, Failures: 12, Errors: 0
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
run.util:
[java]
--
run.clustering:
--
[java] FAILURES!!!
[java] Tests run: 9, Failures: 4, Errors: 0
--
2006/1/3, Kees Jongenburger [EMAIL PROTECTED]:
Yes, this will finally kill the community. lets make the dev mailing a
spam list !
I would not have initiated this, if I would not have been reasonably
sure that the remaining test-cases could be fixed in a few days. After
that, this mail should
Michiel Meeuwissen wrote:
Sadly I sent a few too much yesterday, because I was testing the
script itself, and thinking that mailing did not work. I think it
sent all tests after I subscribed the nightly build user...
I think it would be a good idea to send a periodical result of a run of
Pierre van Rooden wrote:
Michiel Meeuwissen wrote:
Sadly I sent a few too much yesterday, because I was testing the
script itself, and thinking that mailing did not work. I think it
sent all tests after I subscribed the nightly build user...
I think it would be a good idea to send a
run.dbsq:
--
[java] FAILURES!!!
[java] Tests run: 192, Failures: 12, Errors: 0
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
run.util:
[java]
--
run.clustering:
--
[java] FAILURES!!!
[java] Tests run: 9, Failures: 4, Errors: 0
--
run.dbsq:
--
[java] FAILURES!!!
[java] Tests run: 192, Failures: 12, Errors: 0
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
[java] FAILURES!!!
[java] Tests run: 250, Failures: 0, Errors: 1
--
run.util:
[java]
--
run.clustering:
--
[java]
Oops, it's working already...
So, FYI. As of now, it the build fails, or not all test-cases succeed.
Similar mails will automaticly go to this list.
I think of the failing test-cases only the 'dbsq' ones would fail next
night, so it should be quite easiy to make sure that this mail is not
sent
run.dbsq:
--
[java] FAILURES!!!
[java] Tests run: 192, Failures: 12, Errors: 0
--
run.typerel:
--
run.bridge:
--
run.bridge.rmmci:
--
run.util:
[java]
--
run.clustering:
--
[java] FAILURES!!!
[java] Tests run: 9, Failures: 4, Errors: 0
--
Yes, this will finally kill the community. lets make the dev mailing a
spam list !
Dear Kees,
Thanks for your supporting comments! Do you also have a suggestion on
how to improve the communication about the status of the test-cases (and
thereby the 1.8 release) to the community?
Regards,
101 - 124 of 124 matches
Mail list logo