Right after pressing send I saw the reason:
> git rev-parse refs/remotes/origin/pr/9/head^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/pr/9/head^{commit} # timeout=10
Checking out Revision f225bbda63e560f5d5fbf4cb470ec6199e4c8691
(refs/remotes/origin/pr/9/head)
> git config core.sparsecheckout # timeout=10
> git checkout -f f225bbda63e560f5d5fbf4cb470ec6199e4c8691
The default "pr/9" was used for the build somehow instead of ".../pr/147",
thus it was loading an old PR and trying to build it against Java 8, which
is doomed to fail this way now.
Dominik.
On Mon, May 13, 2019 at 9:07 PM Dominik Stadler <dominik.stad...@gmx.at>
wrote:
> Hm,
>
> these did work at some point, e.g. there is a successful build from
> 07-May-2019
> 01:35
> <https://builds.apache.org/view/P/view/POI/job/POI-DSL-Github-PullRequests/9/>
>
> But here somehow a very old verison of POI sources is checked out on the
> build-node, the build.xml contains <property name="version.id"
> value="3.11-beta1-pellucid-6"/>, maybe this machine was not used for a long
> time and for some reason fetching recent sources did not work, but hard to
> say for sure.
>
> I wiped the workspace and triggered the build again to see if it works
> then.
>
> Dominik.
>
> On Mon, May 13, 2019 at 11:14 AM kiwiwings <kiwiwi...@apache.org> wrote:
>
>> Hi Alain,
>>
>> I've fixed the mkdir statement, but now it's failing with some JaCoCo
>> environment error further down the road.
>> I guess the PullRequests job never really worked, but I will have another
>> look onto it ... preferably it would be better, if someone more
>> Git(Hub)-affine would have a look at it too, as I haven't verified if
>> "origin/pr/9/head" is our Git trunk branch.
>>
>> Andi
>>
>>
>>
>> --
>> Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
>> For additional commands, e-mail: dev-h...@poi.apache.org
>>
>>
