[Yade-dev] buildbot warnings in Yade on yade-full

2018-11-23 Thread buildbot
The Buildbot has detected a problem in the build on builder yade-full while building Yade. Full details are available at: https://yade-dem.org/buildbot/builders/yade-full/builds/4918 Buildbot URL: https://yade-dem.org/buildbot/ Buildslave for this Build: r0calcul9 Build Reason: The web-page 'r

[Yade-dev] buildbot warnings in Yade on yade-full

2018-11-23 Thread buildbot
The Buildbot has detected a problem in the build on builder yade-full while building Yade. Full details are available at: https://yade-dem.org/buildbot/builders/yade-full/builds/4917 Buildbot URL: https://yade-dem.org/buildbot/ Buildslave for this Build: r0calcul9 Build Reason: The Nightly sch

[Yade-dev] [Bug 1804621] Re: bodyNumInteractionsHistogram broken

2018-11-23 Thread Bruno Chareyre
If you have time now to make sure nothing is left behind broken it is perfectly fine. Else a revert is not a curse and it takes much less time: no impact on you as you can still use the non-reverted version locally, no bad side effects on others. -- You received this bug notification because y

[Yade-dev] [Bug 1804621] Re: bodyNumInteractionsHistogram broken

2018-11-23 Thread Jérôme Duriez
I'll try to avoid exaggeration here. My commit [1] was about a Shop / utils function, maybe not exactly a bottom layer of yade (at least, not in my opinion). As illustrated by the present bug and the launchpad question, [1] could be problematic in case of Python code (hardcoded in trunk or in user

[Yade-dev] [Bug 1804621] Re: bodyNumInteractionsHistogram broken

2018-11-23 Thread Bruno Chareyre
Incidentally, two students of mines got strange script failures this week and I realize only now that it was exactly this bug. I don't want to open a new bug report but it seems "[1] is not well tested" could be one. Please Jerome consider, carefully, the option of reverting the initial commit.

[Yade-dev] [Bug 1804621] Re: bodyNumInteractionsHistogram broken

2018-11-23 Thread Bruno Chareyre
> several uses of aabb tuple stuff in /py/pack/_packPredicates.cpp which is untouched for now and requires more time I feel uneasy about that. So, the list of potentially broken stuff after [1] includes some of Robert's list #1 plus /py/pack/_packPredicates? Is it right? Can there be other broken

[Yade-dev] [Bug 1804621] Re: bodyNumInteractionsHistogram broken

2018-11-23 Thread Robert Caulk
Thanks Jerome, I guess I did not understand the original proposal to only change the argument type of bodyNumInteractionsHistogram. Seems to be a better solution than changing each of the other functions I pointed out. -- You received this bug notification because you are a member of Yade develop

[Yade-dev] buildbot warnings in Yade on yade-full

2018-11-23 Thread buildbot
The Buildbot has detected a problem in the build on builder yade-full while building yade. Full details are available at: https://yade-dem.org/buildbot/builders/yade-full/builds/4916 Buildbot URL: https://yade-dem.org/buildbot/ Buildslave for this Build: r0calcul9 Build Reason: scheduler Build

[Yade-dev] [Bug 1804621] Re: bodyNumInteractionsHistogram broken

2018-11-23 Thread Jérôme Duriez
See commit https://github.com/yade/trunk/commit/7c60d78bd9badfa174fb79a82af7b119abf81d5d. It fixes the example in the above and the related Launchpad question (I guess, since there was no MWE therein ;-) ). There are also several uses of aabb tuple stuff in /py/pack/_packPredicates.cpp which is un

[Yade-dev] [Bug 1804621] Re: bodyNumInteractionsHistogram broken

2018-11-23 Thread Jérôme Duriez
** Changed in: yade Assignee: (unassigned) => Jérôme Duriez (jduriez) -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1804621 Title: bodyNumInteractionsHistogram broken Status in Yade: New