[
https://issues.apache.org/jira/browse/JENA-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Øyvind Gjesdal reopened JENA-2052:
----------------------------------
I've looked at the windows environment/issues, and have noticed that there is
more space on the c: disk. It was also suggested as a workaround in the
actions/actions-environment issues to manually clone there instead.
There's also a manual switch for running the action so it has to be fired from
the GUI or API.
There is an issue open for the slow
[https://github.com/actions/virtual-environments/issues/1336] macOs runners, so
hopefully it is a question of time. There is also [a mention of a deprecation
of a datasenter and
migration|https://github.com/actions/virtual-environments/issues/2707#issuecomment-782056996]
within the next two months, so hopefully it will improve.
Incoming PR.
> run github action maven.yml also for windows server and macos
> -------------------------------------------------------------
>
> Key: JENA-2052
> URL: https://issues.apache.org/jira/browse/JENA-2052
> Project: Apache Jena
> Issue Type: New Feature
> Components: Build
> Reporter: Øyvind Gjesdal
> Assignee: Andy Seaborne
> Priority: Minor
> Fix For: Jena 4.0.0
>
>
> I've looked at the documentation for github actions
> [https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-running-with-more-than-one-operating-system]
> and have wanted to try out running jobs on multiple OS'es.
>
> Incoming PR (WIP) if it is of interest :) I've not used jira/github before,
> but I think I should check out a branch named by the Jena issue, created from
> this request?
>
> Both windows and macos currently report failing tests from main branch:
> (under Build with maven)
> windows:
> [https://github.com/OyvindLGjesdal/jena/runs/1930240867?check_suite_focus=true]
> macos:
> [https://github.com/OyvindLGjesdal/jena/runs/1930240890?check_suite_focus=true]
>
> I've not found out yet how to continue the CI tasks in the other OS'es if one
> of them fails, while still returning an error on completion. The second
> commit completes green when the continue on error: true is set, however there
> is no indication they failed, without viewing the job.
>
> I thought maybe "if: sucess() | failure()" would work, but it seems the other
> jobs are still canceled, when the first one fails. I'll see if I can read a
> bit more to understand how this works and if it is possible.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
