Re: [jakartaee-tck-dev] Weekly building of Jakarta Platform Stand-alone

[Alwin Joseph <alwin.joseph@xxxxxxxxxx>]

The  job https://ci.eclipse.org/jakartaee-tck/job/standalonetck-nightly-build-run-master/49 completed without the OOM error. I think the publish-junit-test-result report(https://ci.eclipse.org/jakartaee-tck/job/standalonetck-nightly-build-run-master/49/testReport) is not available due to this config change.

But we can view the Junit reports at https://ci.eclipse.org/jakartaee-tck/job/standalonetck-nightly-build-run-master/49/junit-reports-with-handlebars/testSuitesOverview.html as the JUnitReportPublisher plugin work without errors.

Regards,
Alwin

On 03/06/20 9:41 AM, Alwin Joseph wrote:

The **/*-junit-report.xml files are the ones used to create a Junit report in the master job and probably publish-results will fail now. Maybe the publish itself could be removed for testing. Will wait for the job completion.

Regards,
Alwin

On 03/06/20 6:45 AM, Scott Marlow wrote:

Would it help to temporarily remove all of the **/*-junit-report.xml files, to see if that helps the OOM go away?

As a quick test, I'm changing the standalonetck-nightly-build-run-master "Test report XMLs" field from "**/*-junit-report.xml", to "**/DELETE*-junit-report.xml", to see if avoiding the collection/publishing of test results avoids the OOM.

After this test, we can remove the word "DELETE" (or restore from job config history).

Results will be in https://ci.eclipse.org/jakartaee-tck/job/standalonetck-nightly-build-run-master/49.

_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev