Re: [lldb-dev] increase timeout for tests?
On Thu, Mar 8, 2018 at 10:29 AM, Greg Clayton wrote: > It would be great to look into these and see what is taking so long. Some > tests are doing way too much work and should be split up. But it would be > great to see if we have any tests that are not good tests and are just taking > too much time for no reason (like the watchpoint tests were that Pavel fixed). > I tend to agree with you. This is important. Pavel, is there a systematic way you use to profile test cases? Maybe we should consider having a testsuite mode where we warn for slow tests (or revamp the profiling mechanism, if there's one). Thanks! ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] increase timeout for tests?
It would be great to look into these and see what is taking so long. Some tests are doing way too much work and should be split up. But it would be great to see if we have any tests that are not good tests and are just taking too much time for no reason (like the watchpoint tests were that Pavel fixed). Greg > On Mar 8, 2018, at 9:11 AM, Davide Italiano via lldb-dev > wrote: > > Hi, > I've noticed some of the tests we have trigger timeouts when running in debug. > > TIMEOUT: test_NSError_p_dwarf (lang/objc/foundation/TestObjCMethods2.py) > TIMEOUT: test_expression_lookups_objc_dwarf > (lang/objc/foundation/TestObjCMethods.py) > TIMEOUT: test_expressions_in_literals_dsym > (lang/objc/objc-new-syntax/TestObjCNewSyntax.py) > TIMEOUT: test_frame_var_after_stop_at_interface_gmodules > (lang/objc/real-definition/TestRealDefinition.py) > TIMEOUT: test_frame_variable_across_modules_gmodules > (lang/objc/hidden-ivars/TestHiddenIvars.py) > TIMEOUT: test_kvo_with_run_command_gmodules > (functionalities/data-formatter/data-formatter-objc/TestDataFormatterObjC.py) > TIMEOUT: test_long_long_type_gmodules (types/TestIntegerTypesExpr.py) > TIMEOUT: test_long_type_gmodules (types/TestIntegerTypes.py) > TIMEOUT: test_rdar11106605_with_run_command_gmodules > (functionalities/data-formatter/data-formatter-objc/nsstring/TestDataFormatterNSString.py) > TIMEOUT: test_sb_api_listener_event_process_state > (api/multithreaded/TestMultithreaded.py) > TIMEOUT: test_scope_ambiguity_after_using_lookup_with_run_command_gmodules > (lang/cpp/namespace/TestNamespaceLookup.py) > TIMEOUT: test_set_auto_confirm_gmodules (settings/TestSettings.py) > TIMEOUT: test_step_over_load_gmodules > (functionalities/load_unload/TestLoadUnload.py) > TIMEOUT: test_uint32_t_gmodules (lang/cpp/enum_types/TestCPP11EnumTypes.py) > > There's nothing fundamentally broken with these tests, it's just that > they take forever. > What do you think about increasing the timeout for single tests? > Alternatively, we could start splitting these tests into smaller > tests. > > Thanks, > > -- > Davide > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] increase timeout for tests?
Hi, I've noticed some of the tests we have trigger timeouts when running in debug. TIMEOUT: test_NSError_p_dwarf (lang/objc/foundation/TestObjCMethods2.py) TIMEOUT: test_expression_lookups_objc_dwarf (lang/objc/foundation/TestObjCMethods.py) TIMEOUT: test_expressions_in_literals_dsym (lang/objc/objc-new-syntax/TestObjCNewSyntax.py) TIMEOUT: test_frame_var_after_stop_at_interface_gmodules (lang/objc/real-definition/TestRealDefinition.py) TIMEOUT: test_frame_variable_across_modules_gmodules (lang/objc/hidden-ivars/TestHiddenIvars.py) TIMEOUT: test_kvo_with_run_command_gmodules (functionalities/data-formatter/data-formatter-objc/TestDataFormatterObjC.py) TIMEOUT: test_long_long_type_gmodules (types/TestIntegerTypesExpr.py) TIMEOUT: test_long_type_gmodules (types/TestIntegerTypes.py) TIMEOUT: test_rdar11106605_with_run_command_gmodules (functionalities/data-formatter/data-formatter-objc/nsstring/TestDataFormatterNSString.py) TIMEOUT: test_sb_api_listener_event_process_state (api/multithreaded/TestMultithreaded.py) TIMEOUT: test_scope_ambiguity_after_using_lookup_with_run_command_gmodules (lang/cpp/namespace/TestNamespaceLookup.py) TIMEOUT: test_set_auto_confirm_gmodules (settings/TestSettings.py) TIMEOUT: test_step_over_load_gmodules (functionalities/load_unload/TestLoadUnload.py) TIMEOUT: test_uint32_t_gmodules (lang/cpp/enum_types/TestCPP11EnumTypes.py) There's nothing fundamentally broken with these tests, it's just that they take forever. What do you think about increasing the timeout for single tests? Alternatively, we could start splitting these tests into smaller tests. Thanks, -- Davide ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 36630] LLDB SB API headers not installed anymore since r309021
https://bugs.llvm.org/show_bug.cgi?id=36630 lab...@google.com changed: What|Removed |Added Assignee|lldb-dev@lists.llvm.org |lab...@google.com Status|NEW |ASSIGNED CC||lab...@google.com --- Comment #1 from lab...@google.com --- I ran into this last month as well, but follow up on it yet. I'll put up a patch for that soon. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] LLVM 6.0.0 Release
I am pleased to announce that LLVM 6 is now available. Get it here: https://llvm.org/releases/download.html#6.0.0 This release is the result of the community's work over the past six months, including: retpoline Spectre variant 2 mitigation, significantly improved CodeView debug info for Windows, GlobalISel by default for AArch64 at -O0, improved scheduling on several x86 micro-architectures, Clang defaults to -std=gnu++14 instead of -std=gnu++98, support for some upcoming C++2a features, improved optimizations, new compiler warnings, many bug fixes, and more. For more details, see the release notes: https://llvm.org/releases/6.0.0/docs/ReleaseNotes.html https://llvm.org/releases/6.0.0/tools/clang/docs/ReleaseNotes.html https://llvm.org/releases/6.0.0/tools/clang/tools/extra/docs/ReleaseNotes.html https://llvm.org/releases/6.0.0/tools/lld/docs/ReleaseNotes.html Thanks to everyone who helped with filing, fixing, and code-reviewing for release-blocking bugs! Special thanks to the release testers and packagers: Andrew Kelley, Bero Rosenkränzer, Brian Cain, Diana Picus, Dimitry Andric, Jonas Hahnfeld, Michał Górny, Simon Dardis, Sylvestre Ledru, Takumi Nakamura, and Vedant Kumar! For questions or comments about the release, please contact the community on the mailing lists. Onwards to LLVM 7! Thanks, Hans ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
