https://bz.apache.org/bugzilla/show_bug.cgi?id=63762
--- Comment #7 from isuk <[email protected]> --- (In reply to isuk from comment #5) > (In reply to Philippe Mouawad from comment #4) > > (In reply to isuk from comment #3) > > > Sorry I didn't target anyone. I was giving my opinion as it will help > > > anyone > > > like myself who is expecting a resolution for a genuine issue and not > > > getting notified of its whereabout statuses. > > > > > > If you didn’t uncheck notify when updated, then you should have received 3 > > to 4 mails indicating that issue is fixed. > > But if you use mailinator I’m not sure you follow those mails. > > Also, 63723: was a distributed > > > load test related issue and I don't understand how anyone not found this > > > issue before. > > > > Because issue happens when there is a delay between test end on slaves and > > you had a hanging request due to missing timeout on requests as per best > > practices.If slaves end at the same time, you won’t get the issue > > > > > > > > I haven't received nor any email regarding any feedback for the resolution > > > of 63723. I can see you've just done some the git commits. Could you let > > > me > > > know what is the fix is all about? > > > > The fix fixes the way we detect all agents have ended test and we generate > > only after that > > > > Will this fix resolve workers/slaves not > > > finishing threads correctly issue? > > > > it should, but we are waiting for your confirmation > > > > > > This fix is available with JMeter 5.2 I believe. If so, when will be the > > > next release? how long we have to wait? > > > > You can already test nightly build. > > We ‘ll probably release this month > > how can I get the nightly build? where it is available? > > > > > > > For this issue, we need more details as per previous comment > will send you over soon. I learned that this happens due to this scenario: 1. Create a new Test Plan, do a simple HTTP(s) Test Script Recorder and saved it to a new Test Folder. 2. Then try to do file> save Test plan as > the same test plan (delete the previously recorded samplers (from Recording Controller) and record a new test to the same test plan using Test Script Recorder to a NEW Folder) and run the test using non-GUI mode. you should able to see the error. Note: Also, I would like to know whether using HTTP(s) Test Script Recorder is accurate? We are using the recorder for simple function and its recording for load test scenarios. I learned that for e.g. timings, when recording using HTTP recorder and run, is different from when you manually time the same using a stopwatch. Timings are varied like in good seconds. We use HTTP Requests Defaults, Recording Controller and HTTP(s) Test Script Recorder for simple functionality recording and then to load tests. Let me know (reply for the original bug and for my question) Thank you. -- You are receiving this mail because: You are the assignee for the bug.
