Isn't a stacktrace pointless given that this would happen during finalize?
It wouldn't say anything about where the problem is.
Regards
Scott
On 10/06/2017 07:21, "Jacques Le Roux" wrote:
> Actually I just added "\n Please report by creating an OFBIZ-9297 subtask
The Buildbot has detected a restored build on builder
ofbiz-trunk-framework-plugins while building . Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk-framework-plugins/builds/147
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: lares_ubuntu
Build
Hi Taher, Michael
Sorry guys, missed this ugly one due to a previouysly abandoned refactoring and stupidly trusting an IDE suggestion. I did not see your messages
because I was "in the flow" and did not retrieves emails. I then saw Buildbot and your messages, a bit late I must say...
Fixed
The Buildbot has detected a restored build on builder ofbiz-trunk-framework
while building . Full details are available at:
https://ci.apache.org/builders/ofbiz-trunk-framework/builds/188
Buildbot URL: https://ci.apache.org/
Buildslave for this Build: silvanus_ubuntu
Build Reason: The
I agree that we should not use buildbot as the first instance to test
changes for a commit. This has to be done by the committer in his own
sandbox, with no other present changes. I know it's more complicated
using svn instead of git, where you can more easily work on different
feature
Hi Jacques, the build is still crashing, and I suspect this is from your
commit r1798335. Again, this means you're committing without testing and
doing "gradlew cleanAll loadDefault testIntegration".
I also think this mass searching for try blocks in the code base and
changing them to