JDT.Core Components - Track I Build test results

[mpalat]

refer: https://www.eclipse.org/lists/jdt-dev/msg02441.html

Check the I build failures - https://download.eclipse.org/eclipse/downloads/index.html

The following components will be tracked:

jdt.apt.pluggable.tests
jdt.apt.tests
jdt.compiler.apt.tests
jdt.compiler.tool.tests
jdt.core.tests.builder
jdt.core.tests.compiler
jdt.core.tests.model
jdt.core.tests.performance

Most Recent ones:

• I20241230-0520
• I20241201-1800](https://download.eclipse.org/eclipse/downloads/drops4/I20241201-1800)
• I20241120-1800 - one failure captured in issue BuildpathTests.testChangeZIPArchive1 fails #3036
• I20241027-1800 - 2 seemingly new failures in search
• I20241026-1800 - No failure
• I20241025-1840 - Usual suspect
• I20241026-1800 - No Failures
• I20241024-1800 - Usual suspects
• I20241023-1800 - Usual suspect
• I20241022-1800 - No errors
• I20241022-1800
• I20241022-0020
• I20241021-0550
• I20241020-1800 - 2 failures
• I20241020-0600
• I20241019-1800 - no errors
• I20241019-0120
• I20241017-2140
• I20241016-2000
• I20241016-0020
• I20241015-1820
• I20241014-1810
• I20241014-0530
• I20241013-1800

Once the I build failures are checked, please mention the I build version and if there are issues, please create appropriate issues and mention the issue numbers

Notes:
Let's say you are searching for "testBug573589_StaticImport", then the following may help:

(1) Use a command line like the one listed below for finding similar issues
gh issue list --search "test in:title"|grep testBug573589_StaticImport

(2) probably use a 4 digit number for n in case the above does not yield any result
gh issue list --limit <n> |grep testBug573589_StaticImport

(3) For as long as its alive, please check the good old Bugzilla as well

[mpalat]

@subyssurendran666 Could you please also sign up for this?

[subyssurendran666]

Yes @mpalat

[mpalat]

All the assignees, please feel free to opt out in case you are not able to. Took the liberty of assigning people. Thanks!

[srikanth-sankaran]

This just appears to put together a mechanism - more important I feel is the process. So with seven assignees, what is the recommended process ? Would all seven be looking at I builds every day and triage any issues ? That sounds like duplication of effort on the one hand and an unclear work assignment on the other.

How about we come up with a weekly primary owner for tracking build issues and incoming defect reports ? That person can involve others selectively as needed ?

[mpalat]

How about we come up with a weekly primary owner for tracking build issues and incoming defect reports ? That person can involve others selectively as needed ?

@srikanth-sankaran Yes, agree. I can volunteer to be the primary owner for this week [Tue, Mon] - please note the [] brackets - both days inclusive :). Someone else can volunteer for the next week starting next Tuesday. what say?

[srikanth-sankaran]

How about we come up with a weekly primary owner for tracking build issues and incoming defect reports ? That person can involve others selectively as needed ?

@srikanth-sankaran Yes, agree. I can volunteer to be the primary owner for this week [Tue, Mon] - please note the [] brackets - both days inclusive :). Someone else can volunteer for the next week starting next Tuesday. what say?

That sounds good. I would not burden volunteers (@stephan-herrmann for example) - except when they are needed to be involved as per initial analysis.

Also would exclude those whose have cross project responsibilities (@iloveeclipse for example).

We should also agree on the responsibilities:

- Tracking build/test problems and raising follow up issues.
- Tracking and triaging incoming defect reports
- what else ? 

[srikanth-sankaran]

I am happy to participate and take weekly ownership on a rotational basis - Nevertheless, I will remove my name from assignees of this ticket, so this doesn't clutter my queries.

[mpalat]

That sounds good. I would not burden volunteers (@stephan-herrmann for example) - except when they are needed to be involved as per initial analysis.

Also would exclude those whose have cross project responsibilities (@iloveeclipse for example).

Am fine for the above exclusion. However, would leave it to their discretion. Would say this is voluntary rather than mandatory.

We should also agree on the responsibilities:

- Tracking build/test problems and raising follow up issues.
- Tracking and triaging incoming defect reports
- what else ? 

I have created a label "build test failure" which is slightly less "serious" than the label "regression" which says "Something was broken by a previous change". would propose to assign this label to the occasional build test failures. This can be an additional task.

Tracking and triaging incoming defect reports is the inbox tracking category. Would you prefer the same person to do both during the same time.?
See issue #3081 for the first issue under this category.

[stephan-herrmann]

That sounds good. I would not burden volunteers (@stephan-herrmann for example) - except when they are needed to be involved as per initial analysis.
Also would exclude those whose have cross project responsibilities (@iloveeclipse for example).

Am fine for the above exclusion. However, would leave it to their discretion. Would say this is voluntary rather than mandatory.

I'll gratefully make use of that option :)

Of course you may notify me on individual issues, when you see a potential connection to my contributions.

[mpalat]

@jarthana will be the primary owner for this week.

[mpalat]

we have 31 failures listed at https://download.eclipse.org/eclipse/downloads/drops4/I20241128-0520/testresults/html/org.eclipse.jdt.core.tests.model_ep435I-unit-win32-x86_64-java17_win32.win32.x86_64_17.html - investigating

[mpalat]

we have 31 failures listed at https://download.eclipse.org/eclipse/downloads/drops4/I20241128-0520/testresults/html/org.eclipse.jdt.core.tests.model_ep435I-unit-win32-x86_64-java17_win32.win32.x86_64_17.html - investigating

This was transient - ref I20241201-1800

[mpalat]

issue #3499 raised for- regression found in I20241230-0520