Skip to content

#295 - Setting -100,-100 location for window for tests purposes on Li… #205

#295 - Setting -100,-100 location for window for tests purposes on Li…

#295 - Setting -100,-100 location for window for tests purposes on Li… #205

Triggered via push November 5, 2023 21:54
Status Success
Total duration 10m 32s
Artifacts

posmulten.yml

on: push
Compilation and unit tests
1m 44s
Compilation and unit tests
Database creation tests for multiple postgres versions 9.6, 10, 11, 12, 13
1m 12s
Database creation tests for multiple postgres versions 9.6, 10, 11, 12, 13
Testing configuration jar
1m 24s
Testing configuration jar
Integration and functional tests in postgresql-core module
2m 15s
Integration and functional tests in postgresql-core module
E2E smoke tests for configuration jar
1m 52s
E2E smoke tests for configuration jar
Tests for configuration jar documentations
1m 33s
Tests for configuration jar documentations
Testing Swing Application
1m 6s
Testing Swing Application
Running integration and functional tests that checks if code is compatible with postgres versions...
6m 3s
Running integration and functional tests that checks if code is compatible with postgres versions...
Publish to the Maven Central Repository
3s
Publish to the Maven Central Repository
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
Database creation tests for multiple postgres versions 9.6, 10, 11, 12, 13
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Testing configuration jar
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Compilation and unit tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Testing Swing Application
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Tests for configuration jar documentations
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
E2E smoke tests for configuration jar
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Integration and functional tests in postgresql-core module
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Running integration and functional tests that checks if code is compatible with postgres versions...
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, cactuslab/maven-toolchains-xml-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/