Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] where to publish TCK results?

And where exactly should it be published?

Scott Stark wrote on 7/13/19 10:34 AM:
> I would say just the most concise console summary is sufficient.
> 
>> On Jul 13, 2019, at 3:49 AM, arjan tijms <arjan.tijms@xxxxxxxxx
>> <mailto:arjan.tijms@xxxxxxxxx>> wrote:
>>
>> Hi,
>>
>> I was wondering the exact same thing. Some guidance would be useful here.
>>
>> Kind regards,
>> Arjan
>>
>> On Sat, Jul 13, 2019 at 12:34 AM Bill Shannon <bill.shannon@xxxxxxxxxx
>> <mailto:bill.shannon@xxxxxxxxxx>> wrote:
>>
>>     We're supposed to publish TCK (summary) results in a "stable" location.
>>
>>     Where should we publish them for an EE4J project?
>>
>>     And what exactly should they include?
>>
>>
>>     For example, I have this job:
>>     https://jenkins.eclipse.org/javamail/job/eftl-mailtck-build-run/
>>
>>     Which includes this junit-format summary:
>>     https://jenkins.eclipse.org/javamail/job/eftl-mailtck-build-run/lastSuccessfulBuild/artifact/junitreports/mailtck-junit-report.xml
>>     (sorry, you might not be able to access that)
>>
>>     Or I could publish this summary output from the console output:
>>
>>     [javatest.batch] Number of tests completed:  321 (321 pass, 0 fail, 0 errors)
>>     [javatest.batch]
>>     ***************************************************************
>>     [javatest.batch] Completed running 321 tests.
>>     [javatest.batch] Number of Tests Passed      = 321
>>     [javatest.batch] Number of Tests Failed      = 0
>>     [javatest.batch] Number of Tests with Errors = 0
>>     [javatest.batch] Number of Tests Not Run     = 0
> …
> 
> 
> 
> _______________________________________________
> jakarta.ee-spec.committee mailing list
> jakarta.ee-spec.committee@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
> 


Back to the top