I partly agree. There seem to be a
couple of similar tests that did not get the change to use the new
EventFilters.filtered() method. Perhaps there is something unique
about those tests that prevented them from failing, but I'm not so
sure that's a good reason for not applying this change to them
also. However, it's not a requirement that all tests (and users of
EventFilters) confine the desired events to those in the debuggee
main class. There could be more than one class being debugged, and
the test may want to see events for these other test classes.
Chris On 6/11/18 6:18 PM, serguei.spit...@oracle.com wrote:
|
- Re: RFR 8203809: [Graal] JDI tests fai... serguei.spit...@oracle.com
- Re: RFR 8203809: [Graal] JDI tests fai... Chris Plummer
- Re: RFR 8203809: [Graal] JDI tests... serguei.spit...@oracle.com
- Re: RFR 8203809: [Graal] JDI t... Daniil Titov
- Re: RFR 8203809: [Graal] ... serguei.spit...@oracle.com
- Re: RFR 8203809: [Graal] ... daniil . x . titov
- Re: RFR 8203809: [Graal] ... Daniil Titov
- Re: RFR 8203809: [Graal] ... serguei.spit...@oracle.com
- Re: RFR 8203809: [Graal] ... Chris Plummer
- Re: RFR 8203809: [Graal] JDI tests fail wi... serguei.spit...@oracle.com
- Re: RFR 8203809: [Graal] JDI tests fail with: J... Chris Plummer