Re: [Lldb-commits] [lldb] 1b1d981 - Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter.""

2020-10-01 Thread Jim Ingham via lldb-commits
Thanks for the info… We’re running in sync mode, so for Continue to return before the process is all the way stopped, Process::ResumeSynchronous() must be bobbling the case where a stop event that resumes the process comes in. The only way I can see that happening is if Process::PrivateResume

Re: [Lldb-commits] [lldb] 1b1d981 - Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter.""

2020-10-01 Thread Raphael “Teemperor” Isemann via lldb-commits
+1, I have two machines with very similar setup where only the one that is under heavy load sees the test failures. - Raphael > On 1 Oct 2020, at 14:24, Pavel Labath wrote: > > On 30/09/2020 23:21, Jim Ingham wrote: >> The test doesn’t seem to be flakey in the “run it a bunch of times and >>

Re: [Lldb-commits] [lldb] 1b1d981 - Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter.""

2020-10-01 Thread Pavel Labath via lldb-commits
On 30/09/2020 23:21, Jim Ingham wrote: > The test doesn’t seem to be flakey in the “run it a bunch of times and > it will eventually fail” type flakey.  I ran the test 200 times on my > machine and didn’t get a failure. Actually, it seems like exactly the typical kind of flaky test to me -- it

Re: [Lldb-commits] [lldb] 1b1d981 - Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter.""

2020-09-30 Thread Pavel Labath via lldb-commits
On 30/09/2020 20:45, Jim Ingham wrote: > I also used to get e-mails when a test failed and I was on the changes list. > But I haven’t gotten any failure e-mails. Does that only happen for some of > the bots (or has that stopped working) or should I look to my filters? > > Jim > You didn't

Re: [Lldb-commits] [lldb] 1b1d981 - Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter.""

2020-09-30 Thread Jim Ingham via lldb-commits
I also used to get e-mails when a test failed and I was on the changes list. But I haven’t gotten any failure e-mails. Does that only happen for some of the bots (or has that stopped working) or should I look to my filters? Jim > On Sep 30, 2020, at 10:40 AM, Jim Ingham via lldb-commits >

Re: [Lldb-commits] [lldb] 1b1d981 - Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter.""

2020-09-30 Thread Jim Ingham via lldb-commits
It looks like all the failing builds are incremental builds. Can you kick off a clean build and see if that also gets a failure? I’m worried that all the SWIG bits aren’t getting rebuilt. The code that is failing here is not at all time dependent, or particularly platform specific, so it

Re: [Lldb-commits] [lldb] 1b1d981 - Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter.""

2020-09-30 Thread Pavel Labath via lldb-commits
It looks like the new test (TestStopHookScripted.py) is flaky: http://lab.llvm.org:8011/builders/lldb-x86_64-debian/builds/18360/steps/test/logs/stdio http://lab.llvm.org:8011/builders/lldb-aarch64-ubuntu/builds/9484/steps/test/logs/stdio

[Lldb-commits] [lldb] 1b1d981 - Revert "Revert "Add the ability to write target stop-hooks using the ScriptInterpreter.""

2020-09-29 Thread Jim Ingham via lldb-commits
Author: Jim Ingham Date: 2020-09-29T12:01:14-07:00 New Revision: 1b1d9815987a753f2f3524cfad050b85972dae5b URL: https://github.com/llvm/llvm-project/commit/1b1d9815987a753f2f3524cfad050b85972dae5b DIFF: https://github.com/llvm/llvm-project/commit/1b1d9815987a753f2f3524cfad050b85972dae5b.diff