-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors in tests #6431
Comments
ok now looks like we are getting somewhere: (@loumalouomega )
seems to be the same error |
😮 no clue about what "difference between a singular iterator to a singular iterator" means. |
A singular iterator is an iterator that does not point to any container. its like a sort of uninitialized variable. The error seems to say that it cannot do the difference between undefined and undefined, which makes sense if its the case |
I am trying to get the error in gdb but it resists to fail there xD |
@pooyan-dadvand it seems like this is sth for you => looak at from KratosMultiphysics import *
from KratosMultiphysics.StructuralMechanicsApplication import *
def run():
Tester.SetVerbosity(Tester.Verbosity.TESTS_OUTPUTS) # TESTS_OUTPUTS
Tester.RunTestCases("*TestSPRErrorProcess2*")
if __name__ == '__main__':
run() |
Sometimes the CI fails in FullDebug with this error in the C-Tests:
|
If it is during the structural test it could be in the case of the SPR test, which consider the neighbour elements. This is a OMP thing, and can be solved |
ok |
I'd keep it to see what happens... |
see #6807 (comment) |
@loumalouomega it seems like the SolidShell Element has the same problem as you solved in #6460 |
Huuum, can your paste me the error here? |
I could never reproduce it 😅 even though I tried hard! I think @rubenzorrilla could |
Here it is. |
I think that the problem is that the (I experienced the same problem with the |
ping, is this still not solved? |
no |
I cannot reproduce it |
Neither can I, but @rubenzorrilla could Can you just do what he suggested? Then hopefully it will be solved |
OK |
Fixes #6431 Removed unused NEIGHBOUR_ELEMENTS from the check, and improves NEIGHBOUR_NODES check
Unfortunately I couldn't. The error was thrown by the gcc FullDebug compilation in the CI. In any case, I think that what I post above should fix it. |
I already did the PR to fix it
El mar., 26 may. 2020 14:39, Rubén Zorrilla <notifications@github.com>
escribió:
… Unfortunately I couldn't. The error was thrown by the gcc FullDebug
compilation in the CI. In any case, I think that what I post above should
fix it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6431 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEYQZAEBXSDJ55DX2SYGSVLRTO2BBANCNFSM4KXE2EKQ>
.
|
…heck-sprism [StructuralMechanicsApplication] Fix #6431
Fixes #6431 Removed unused NEIGHBOUR_ELEMENTS from the check, and improves NEIGHBOUR_NODES check
I am constantly running the tests of the Apps in the CI to see if I can reproduce the errors. I am compiling in FullDebug with
GLIBCXX_DEBUG
and run the small-suite with 2 omp threadsFYI @KratosMultiphysics/technical-committee
I found one in the Fluid (@rubenzorrilla I guess this is yours), which happens randomly
I will report more if I find more:
The text was updated successfully, but these errors were encountered: