| Re: [jakartaee-tck-dev] Unable to access jarfile in test run |
On 6/20/20 10:02 AM, Scott Marlow wrote:
>
>
> On 6/20/20 9:57 AM, Scott Marlow wrote:
>>
>>
>> On 6/20/20 7:14 AM, Scott Marlow wrote:
>>>
>>>
>>> On 6/19/20 7:10 PM, Gurkan Erdogdu wrote:
>>>> Here is the link for the PR
>>>> https://github.com/eclipse-ee4j/jakartaee-tck/pull/342
>>>>
>>>> I appreciate it if you are able to review it.
>>>
>>> Thank you Gurkan for making this change, very much appreciated!
>>>
>>> https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-nightly-build-master
>>
>>
>>
>> With fewer samples tests failing, down to 6 failures
>> https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/715/testReport/
>>
>
> We should verify that we are starting mail.
>
>>
>>> is building now with your change merged!
>>>
>>
>> https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-nightly-run-master
>> is started (watch
>> https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/716/testReport
>> for progress).
A big improvement from this change,
https://ci.eclipse.org/jakartaee-tck/job/jakartaee-tck/job/master/716/testReport/
shows that we are now only failing around 4465 (10%) of 40,699 tests!
We did stop the test run due to JPA deployment failures that we still
need to understand (e.g. look at server.log).
https://github.com/eclipse-ee4j/mojarra/pull/4726 is now fixed (thanks
Gurkan!) and will address several failures parsing faces-config.xml
(when released + merged in GlassFish master).
There are likely others as well.
Soon we will start running with JDK 11, which will likely increase the
number of failures we see.
Scott