[
https://issues.apache.org/jira/browse/JENA-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287696#comment-17287696
]
Andy Seaborne commented on JENA-2052:
-------------------------------------
Seen the PR - thanks!
Just as background:
The project uses [a number of Jenkins
jobs|https://ci-builds.apache.org/job/Jena/] including one for windows. There's
more control (like triggering them on demand).
The use of Github actions directly by Apache projects, that is, running on the
Apache account, is quite new and because it is one account for all projects,
there are issues with running out of credits (the Foundation does, I believe,
get more than the mininum per account). Its settling down as. Jena is a simple
build, other projects are not.
The windows job passes on Jenkins - so we can deduce that the job does not run
of a filesystem with path including an "~". Good to catch this. Raiused as
JENA-2054.
We don't have regular macOS - the Jenkins installation no longer has mac build
servers so it's good to see that here. (MacOS tests do get done during the
release process.)
The macOS job looks like an environment timing issue - the timeout isn't
happening because the query is executing. Timeout tests are hard to get stable
- sometimes the query runs to completion before the timeout happens due to
scheduling or clock weirdness. But setting the query execution so long to
guarantee the timeout makes local development less nice.
> 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
> Priority: Minor
>
> 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)
