I get an error the following after run make test command in preCICE on Centos 7. Did anyone encounter this problem?
Thank you...
cmake parameters when building
cmake3 .. -DBUILD_SHARED_LIBS=ON -DCMAKE_BUILD_TYPE=Debug -DMPI=ON
-DMPIEXEC_EXECUTABLE=/opt/ohpc/pub/mpi/openmpi3-gnu8/3.1.4/bin/mpiexec
-DCMAKE_INSTALL_PREFIX=/opt $PRECICE_ROOT
[root#headnode build]# make test
Running tests...
Test project /opt/precice-1.6.1/build
Start 1: precice.Base
1/4 Test #1: precice.Base .....................***Failed 0.01 sec
Start 2: precice.MPI_Ports
2/4 Test #2: precice.MPI_Ports ................***Failed 0.01 sec
Start 3: precice.PetRBFParallel
3/4 Test #3: precice.PetRBFParallel ...........***Failed 0.01 sec
Start 4: precice.NoMPI
4/4 Test #4: precice.NoMPI .................... Passed 4.09 sec
25% tests passed, 3 tests failed out of 4
Label Time Summary:
canfail = 0.02 sec*proc (2 tests)
Total Test time (real) = 4.14 sec
The following tests FAILED:
1 - precice.Base (Failed)
2 - precice.MPI_Ports (Failed)
3 - precice.PetRBFParallel (Failed)
Errors while running CTest
make: *** [test] Error 8
Before running test as root enter following :
export OMPI_ALLOW_RUN_AS_ROOT_CONFIRM=1
export OMPI_ALLOW_RUN_AS_ROOT=1
Related
Log from Jenkins:
nx run-many --target=test --projects=a,b,c,d,e,f,g,h --ci --runInBand
> nx run a:test --ci=true --runInBand=true
PASS a/component.spec.ts
PASS a/another-component.spec.ts
> nx run b:test --ci=true --runInBand=true
PASS b/file.spec.ts (147.183 s)
PASS b/another-file.spec.ts (5.116 s)
Test Suites: 54 passed, 54 total
Tests: 277 passed, 277 total
Snapshots: 0 total
Time: 240.571 s
Ran all test suites.
So after running the test for project a, it does not show the output. It is always a bit consistent with 2 projects where the tests run fine.
Maybe it is failing silently somewhere?
[Question posted by a user on YugabyteDB Community Slack]
Debug build does not seem to be working in the clang12 based build:
./yb_build.sh debug --sj
[100%] Linking CXX executable ../../../tests-integration-tests/cdc_service-int-test
[100%] Built target cdc_service-int-test
make: *** [Makefile:101: all] Error 2
real 0m28.279s
user 4m4.235s
sys 0m25.477s
[2022-02-26T15:52:32 yb_build.sh:466 run_cxx_build] C++ build finished with exit code 2 (build type: debug, compiler: clang12). Timing information is available above.
==========================================================================================
YUGABYTE BUILD SUMMARY
==========================================================================================
Build type : debug
C/C++ compiler : clang12
Build architecture : x86_64
Build directory : /yb-source/build/debug-clang12-dynamic
Third-party dir : /opt/yb-build/thirdparty/yugabyte-db-thirdparty-v20211222064150-dd4872fe56-almalinux8-x86_64-clang12
C++ compilation time : 28 seconds
Exit code : 2
------------------------------------------------------------------------------------------
doing
./yb_build.sh debug --clang12 --sj
also results in an error
...
[m-1] In YugabyteDB, setting LC_COLLATE to C and all other locale settings to en_US.UTF-8 by default. Locale support will be enhanced as part of addressing https://github.com/yugabyte/yugabyte-db/issues/1557
[m-1] initdb: invalid locale name "en_US.UTF-8"
[m-1] I0226 15:54:20.630203 15811 pg_wrapper.cc:521] initdb took 124 ms
[m-1] E0226 15:54:20.630272 15811 pg_wrapper.cc:525] initdb failed: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
[m-1] E0226 15:54:20.630429 15811 catalog_manager.cc:7776] initdb failed: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
E0226 15:54:21.075644 15749 external_mini_cluster.cc:1247] master reported an initdb error: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
/yb-source/src/yb/yql/pgwrapper/pg_wrapper_test_base.cc:58: Failure
Failed
Bad status: Runtime error (yb/integration-tests/external_mini_cluster.cc:1248): Failed to start masters.: initdb failed: Runtime error (yb/yql/pgwrapper/pg_wrapper.cc:467): /yb-source/build/debug-clang12-dynamic/postgres/bin/initdb failed with exit code 1
[m-1] W0226 15:54:21.096375 15815 catalog_manager.cc:2084] Tablespace refresh task failed with error Internal error (yb/master/catalog_manager.cc:1929): pg_tablespace table info not found
Test failure stack trace:
/yb-source/src/yb/yql/pgwrapper/pg_wrapper_test_base.cc:58: # 0x7f2962b044e9 yb::pgwrapper::PgWrapperTestBase::SetUp()
/yb-source/src/yb/yql/pgwrapper/create_initial_sys_catalog_snapshot.cc:29: # 0x404d94 yb::pgwrapper::CreateInitialSysCatalogSnapshotTest::SetUp()
I0226 15:54:21.706461 15749 external_mini_cluster.cc:2206] { daemon_id: m-1 bound_rpc: :0 } Starting Shutdown()
I0226 15:54:21.706606 15749 external_mini_cluster.cc:2249] Killing /yb-source/build/debug-clang12-dynamic/tests-pgwrapper/../bin/yb-master with pid 15756 with SIGKILL
I0226 15:54:21.719123 15749 test_util.cc:94] -----------------------------------------------
I0226 15:54:21.719149 15749 test_util.cc:95] Had fatal failures, leaving test files at /tmp/yb_test.tmp.32433.7631.5669.pid15685/create_initial_sys_catalog_snapshot.CreateInitialSysCatalogSnapshotTest.CreateInitialSysCatalogSnapshot.1645890856672495-15749
[ FAILED ] CreateInitialSysCatalogSnapshotTest.CreateInitialSysCatalogSnapshot (5016 ms)
[----------] 1 test from CreateInitialSysCatalogSnapshotTest (5016 ms total)
[----------] Global test environment tear-down
[==========] 1 test from 1 test case ran. (5016 ms total)
[ PASSED ] 0 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] CreateInitialSysCatalogSnapshotTest.CreateInitialSysCatalogSnapshot
1 FAILED TEST
I0226 15:54:21.751582 15748 run-with-timeout.cc:198] subprocess.Wait finished, waitpid() returned 256
...
[postprocess_test_result.py:246] 2022-02-26 15:54:22,577 INFO: Wrote JSON test report file: /yb-source/build/debug-clang12-dynamic/yb-test-logs/tests-pgwrapper__create_initial_sys_catalog_snapshot/CreateInitialSysCatalogSnapshotTest_CreateInitialSysCatalogSnapshot_test_report.json
(end of standard error)
Traceback (most recent call last):
File "/yb-source/python/yb/gen_initial_sys_catalog_snapshot.py", line 83, in <module>
main()
File "/yb-source/python/yb/gen_initial_sys_catalog_snapshot.py", line 74, in main
raise RuntimeError("initdb failed in %.1f sec" % elapsed_time_sec)
RuntimeError: initdb failed in 6.4 sec
make[2]: *** [src/yb/yql/pgwrapper/CMakeFiles/initial_sys_catalog_snapshot.dir/build.make:70: src/yb/yql/pgwrapper/CMakeFiles/initial_sys_catalog_snapshot] Error 1
make[1]: *** [CMakeFiles/Makefile2:51929: src/yb/yql/pgwrapper/CMakeFiles/initial_sys_catalog_snapshot.dir/all] Error 2
make: *** [Makefile:101: all] Error 2
This happens in Alma Linux 8.5. Any hints?
You need some additional packages and it should work:
dnf install langpacks-en glibc-all-langpacks -y
My app engine deployment (flexible environment, node js 12) has suddenly started failing, seemingly due to an issue with node js on the google side.
Build output here:
Step #1: Already have image (with digest): gcr.io/kaniko-project/executor#sha256:f87c11770a4d3ed33436508d206c584812cd656e6ed08eda1cff5c1ee44f5870
Step #1: [36mINFO[0m[0000] Removing ignored files from build context: [node_modules .dockerignore Dockerfile npm-debug.log yarn-error.log .git .hg .svn app.yaml]
Step #1: [36mINFO[0m[0004] Downloading base image gcr.io/google-appengine/nodejs#sha256:ef8be7b4dc77c3e71fbc85ca88186b13214af8f83b8baecc65e8ed85bb904ad5
Step #1: [36mINFO[0m[0019] Taking snapshot of full filesystem...
Step #1: [36mINFO[0m[0035] Using files from context: [/workspace]
Step #1: [36mINFO[0m[0036] COPY . /app/
Step #1: [36mINFO[0m[0036] Taking snapshot of files...
Step #1: [36mINFO[0m[0037] RUN /usr/local/bin/install_node '>=12.0.0'
Step #1: [36mINFO[0m[0037] cmd: /bin/sh
Step #1: [36mINFO[0m[0037] args: [-c /usr/local/bin/install_node '>=12.0.0']
Step #1: % Total % Received % Xferd Average Speed Time Time Time Current
Step #1: Dload Upload Total Spent Left Speed
100 32.1M 100 32.1M 0 0 66.9M 0 --:--:-- --:--:-- --:--:-- 66.8M
Step #1: % Total % Received % Xferd Average Speed Time Time Time Current
Step #1: Dload Upload Total Spent Left Speed
100 3838 100 3838 0 0 23116 0 --:--:-- --:--:-- --:--:-- 23260
Step #1: gpg: Signature made Tue Sep 8 15:43:07 2020 UTC using RSA key ID C17AB93C gpg: Can't check signature: public key not found
Step #1: The Node.js binary could not be verified.
Step #1: This means it may not be an officially released Node.js binary
Step #1: or may have been tampered with.
Step #1:
Step #1: Aborting the installation.
Step #1:
Step #1: The installation can be forced using the --ignore-verification-failure
Step #1: flag. However, it is strongly recommended that you install a version
Step #1: of Node.js that can be verified.
Step #1:
Step #1: Node installation failed: /opt/gcp/runtime/bootstrap_node exited with a non-zero exit code: 1
Step #1: error building image: error building stage: waiting for process to exit: exit status 1
Finished Step #1
ERROR
ERROR: build step 1 "gcr.io/kaniko-project/executor#sha256:f87c11770a4d3ed33436508d206c584812cd656e6ed08eda1cff5c1ee44f5870" failed: step exited with non-zero status: 1
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Is anybody else seeing this issue?
Thanks
Chris
In our case, the thing was that App Engine installed Node 14.10.0 because we had "node": "14.x" in the package.json. Seems like the latest release has some issues.
I fixed deploy by changing the engine to a fixed version:
"engines": {
"node": "14.9"
}
If you are using 12.x - try some of the previous version that worked.
The latest that works is 14.16.0. Add the following in your package.json
...
"engines": {
"node": "14.16.0"
},
...
Then deploy with gcloud app deploy. The GCP issue to follow is https://github.com/GoogleCloudPlatform/nodejs-docker/issues/214
This happens quite often whenever a new Nodejs version is released as GAE builder "is not entirely backwards compatible between minor version upgrades" (Source: https://github.com/GoogleCloudPlatform/nodejs-docker/issues/214#issuecomment-1276728834)
The fix/solution would be to pin down the last version that worked (in most cases, the 2nd most recent that was released: https://nodejs.org/en/download/releases/). You will most likely notice that a nodejs version was released around the time your build started failing.
I have a cucumber test suite which has some tests
I run the tests using command
sbt "testOnly <cucumber_class_name>"
And one of the cucumber tests fail an assertion and console shows
Failed scenarios:
classpath:features/my_cucumber_scenario.feature:31# <my test description>
19 Scenarios (1 failed, 18 passed)
88 Steps (1 failed, 87 passed)sts 214s
3m18.224s
But in the end the console shows
Total 80, Failed 0, Errors 0, Passed 80
Since one of the tests failed, in the final output it should have shown
Failed 1 (Or something like that). But it is showing all passed instead due to which my build on travis is not failing.
How to solve this problem ? Is there a solution in cucumber ?
My dependencies are
"io.cucumber" % "cucumber-core" % "5.7.0",
"io.cucumber" % "cucumber-junit" % "5.7.0"
"io.cucumber" %% "cucumber-scala" % "5.7.0"
This problem is solved by cucumber team in
https://github.com/cucumber/cucumber-jvm-scala/releases/tag/v6.2.2
I am using Jest for testing mu nodejs code an after commiting my code the pipeline runs and Jest test case is throwing error but pipeline is not failing.
In test case it shows there are not expected results and so test case is failing but is not forcing the gitlab pipeline to fail. Any help?
✓ (10 ms)
✓ Test case for creating patient form testing (12 ms)
Test Suites: 1 passed, 1 total
Tests: 2 passed, 2 total
Snapshots: 0 total
Time: 3.174 s
Ran all test suites matching /patient_create.test.js/i.
(node:18484) UnhandledPromiseRejectionWarning: Error: expect(received).not.toBeDefined()
Received: [Error: expect(received).toBe(expected) // Object.is equality·
Expected: 200
Received: 404]```