Andy,
I have been out and about most of this weekend. I will fire up a new vm
tomorrow to replicate the setup you have mentioned.

Best,
Marco


On Sun, Jul 14, 2024 at 4:36 PM Andy Seaborne <a...@apache.org> wrote:

> Hi Marco,
>
> The list of prerequisites for Cypress is list at:
>
>
> https://docs.cypress.io/guides/getting-started/installing-cypress#Linux-Prerequisites
>
> They are all an single "apt install". if you have moment, I'd be
> grateful if you could try that.
>
>
> I installed nodejs with the exact version you have, and the build still
> went fine so it isn't looking like node version leakage.
>
>      Andy
>
> On 13/07/2024 20:41, Marco Neumann wrote:
> > Hi Andy,
> >
> > I don't recall the cypress related error but I had to install quite a few
> > new packages (cross-env, mocha, run-script-os ) to get the tests over the
> > line.
> >
> > Many of the new features go beyond my current use cases for jena so it
> will
> > take a while before I encounter any issues, in particular if they don't
> > interfere with use of the base system.
> >
> > Marco
> >
> >
> >
> > On Sat, Jul 13, 2024 at 4:02 PM Andy Seaborne <a...@apache.org> wrote:
> >
> >>
> >>
> >> On 13/07/2024 10:56, Marco Neumann wrote:
> >>> [X] +1
> >>>
> >>> but not deployed yet
> >>>
> >>> had to install xvfb, pnpm and mocha etc to get it pass the Apache Jena
> -
> >>> Fuseki UI tests
> >>>
> >>> mvn clean install
> >>>
> >>
> >> Hi Marco - thank you for trying it out.
> >>
> >> Did the build output also say "[INFO] [TESTS] Cypress failed to start."
> >> earlier in the log?
> >>
> >> """
> >> [INFO] [TESTS] [STARTED] Task without title.
> >> [INFO] [TESTS] [FAILED] Cypress failed to start.
> >> [INFO] [TESTS] [FAILED]
> >> [INFO] [TESTS] [FAILED] This may be due to a missing library or
> >> dependency. https://on.cypress.io/required-dependencies
> >> [INFO] [TESTS] [FAILED]
> >> """
> >>
> >> The ASF Jenkins instance is experiencing this error and it appears to be
> >> due to dependench related. I this not clear why it has started (the PR
> >> where it started doesn't on the surface seem to a likely looking
> change).
> >>
> >>   > Node v18.19.1
> >>
> >> Hmm - the POM file says
> >>
> >>       <node.version>v20.11.0</node.version>
> >>
> >> so that seems to only apply to the build, not running tests.
> >>
> >>
> >> It could be that the Jena build is now running on older environments -
> >> the ASF Jenkins build fleet has about 30 Ubuntu servers (!!) for general
> >> use and from mixed donations.
> >>
> >> The problem is noted in the pre-release thread:
> >> https://lists.apache.org/thread/drfj9lmh65gcj6d609tx52qdb1n4wrxc
> >>
> >> and because the build is passing on github actions and local machine, it
> >> seems better to get the release out and come back and fix it.
> >> Jena ought to move to using Jenkins pipeline with a docker image so that
> >> the build to get isolation. We fairly recently had problems with nodejs
> >> versions on older build servers but in that case nodejs was updated.
> >>
> >>       Andy
> >>
> >>> [ERROR] Failed to execute goal
> >>> com.github.eirslett:frontend-maven-plugin:1.15.0:yarn (yarn run
> test:e2e)
> >>> on project jena-fuseki-ui: Failed to run task: 'yarn run test:e2e'
> >> failed.
> >>> org.apache.commons.exec.ExecuteException: Process exited with an
> error: 1
> >>> (Exit value: 1) -> [Help 1]
> >>>
> >>> [INFO] Reactor Summary for Apache Jena 5.1.0:
> >>> [INFO]
> >>> [INFO] Apache Jena ........................................ SUCCESS [
> >>>    9.543 s]
> >>> [INFO] Apache Jena - IRI .................................. SUCCESS [
> >>>    2.671 s]
> >>> [INFO] Apache Jena - Base ................................. SUCCESS [
> >>>    3.686 s]
> >>> [INFO] Apache Jena - Core ................................. SUCCESS [
> >>> 28.747 s]
> >>> [INFO] Apache Jena - ARQ .................................. SUCCESS [
> >>> 25.787 s]
> >>> [INFO] Apache Jena - ONTAPI ............................... SUCCESS [
> >>> 10.581 s]
> >>> [INFO] Apache Jena - SHACL ................................ SUCCESS [
> >>>    3.326 s]
> >>> [INFO] Apache Jena - ShEx ................................. SUCCESS [
> >>>    3.885 s]
> >>> [INFO] Apache Jena - RDF Patch ............................ SUCCESS [
> >>>    2.371 s]
> >>> [INFO] Apache Jena - RDF Connection ....................... SUCCESS [
> >>>    2.447 s]
> >>> [INFO] Apache Jena - DBOE Database Operation Environment .. SUCCESS [
> >>>    0.066 s]
> >>> [INFO] Apache Jena - DBOE Base ............................ SUCCESS [
> >>>    2.156 s]
> >>> [INFO] Apache Jena - DBOE Transactions .................... SUCCESS [
> >>>    1.825 s]
> >>> [INFO] Apache Jena - DBOE Indexes ......................... SUCCESS [
> >>>    1.079 s]
> >>> [INFO] Apache Jena - DBOE Index test suite ................ SUCCESS [
> >>>    0.320 s]
> >>> [INFO] Apache Jena - DBOE Transactional Datastructures .... SUCCESS [
> >>> 20.250 s]
> >>> [INFO] Apache Jena - DBOE Storage ......................... SUCCESS [
> >>>    1.694 s]
> >>> [INFO] Apache Jena - TDB1 (Native Triple Store) ........... SUCCESS [
> >>>    7.363 s]
> >>> [INFO] Apache Jena - TDB2 (Native Triple Store) ........... SUCCESS [
> >>>    6.352 s]
> >>> [INFO] Apache Jena - Libraries POM ........................ SUCCESS [
> >>>    0.243 s]
> >>> [INFO] Apache Jena - Command line tools ................... SUCCESS [
> >>>    2.839 s]
> >>> [INFO] Apache Jena - SPARQL Text Search ................... SUCCESS [
> >>>    5.312 s]
> >>> [INFO] Apache Jena - Fuseki - A SPARQL 1.1 Server ......... SUCCESS [
> >>>    0.024 s]
> >>> [INFO] Apache Jena - Fuseki Core Engine ................... SUCCESS [
> >>>    5.540 s]
> >>> [INFO] Apache Jena - Fuseki UI ............................ FAILURE [
> >>>    9.412 s]
> >>> [INFO] Apache Jena - Fuseki Data Access Control ........... SKIPPED
> >>> [INFO] Apache Jena - Fuseki Server Main ................... SKIPPED
> >>> [INFO] Apache Jena - Fuseki Server Jar .................... SKIPPED
> >>> [INFO] Apache Jena - Fuseki Webapp ........................ SKIPPED
> >>> [INFO] Apache Jena - Fuseki WAR File ...................... SKIPPED
> >>> [INFO] Apache Jena - Fuseki Server Standalone Jar ......... SKIPPED
> >>> [INFO] Apache Jena - Fuseki Docker Tools .................. SKIPPED
> >>> [INFO] Apache Jena - Fuseki Binary Distribution ........... SKIPPED
> >>> [INFO] Apache Jena - GeoSPARQL Engine ..................... SKIPPED
> >>> [INFO] Apache Jena - Fuseki with GeoSPARQL Engine ......... SKIPPED
> >>> [INFO] Apache Jena - Integration Testing .................. SKIPPED
> >>> [INFO] Apache Jena - Benchmark Suite ...................... SKIPPED
> >>> [INFO] Apache Jena - Benchmarks Shaded Jena 4.8.0 ......... SKIPPED
> >>> [INFO] Apache Jena - Benchmarks JMH ....................... SKIPPED
> >>> [INFO] Apache Jena - Distribution ......................... SKIPPED
> >>> [INFO] Apache Jena - Security Permissions ................. SKIPPED
> >>> [INFO] Apache Jena - Extras ............................... SKIPPED
> >>> [INFO] Apache Jena - Extras - Query Builder ............... SKIPPED
> >>> [INFO] Apache Jena - CommonsRDF for Jena .................. SKIPPED
> >>> [INFO] Apache Jena - Extras - Service Enhancer ............ SKIPPED
> >>> [INFO] Apache Jena - Code Examples ........................ SKIPPED
> >>> [INFO] Apache Jena - BOM .................................. SKIPPED
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [INFO] BUILD FAILURE
> >>> [INFO]
> >>>
> ------------------------------------------------------------------------
> >>> [ERROR] Failed to execute goal
> >>> com.github.eirslett:frontend-maven-plugin:1.15.0:yarn (yarn run
> test:e2e)
> >>> on project jena-fuseki-ui: Failed to run task: 'yarn run test:e2e'
> >> failed.
> >>> org.apache.commons.exec.ExecuteException: Process exited with an
> error: 1
> >>> (Exit value: 1) -> [Help 1]
> >>> [ERROR]
> >>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the
> >> -e
> >>> switch.
> >>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >>> [ERROR]
> >>> [ERROR] For more information about the errors and possible solutions,
> >>> please read the following articles:
> >>> [ERROR] [Help 1]
> >>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> >>>
> >>>
> >>> Apache Maven 3.9.6
> >>> java version "21" 2023-09-19 LTS
> >>> Linux
> >>> Node v18.19.1
> >>> NPM 9.2.0
> >>
> >
> >
>


-- 


---
Marco Neumann

Reply via email to