cmake add_test NAME warnings - warnings

I have a very strange warning which appears when i run ctest :
Syntax Warning in cmake code at
my_build_path/CTestTestfile.cmake:7:10
A future version of CMake may treat unquoted argument:
[=[myTest]=]
as an opening long bracket. Double-quote the argument.
Call Stack (most recent call first):
CTestTestfile.cmake:10 (subdirs)
This warning is for project developers. Use -Wno-dev to suppress it.
It's look like all my test name have the same problem, cmake add [=[ ]=] before and after all my tests. Here results of ctest -N
Test #1: [=[myTest1]=]
Test #2: [=[myTest2]=]
Test #3: [=[myTest3]=]
Test #4: [=[myTest4]=]
Test #5: [=[myTest5]=]
Test #6: [=[myTest6]=]
Test #7: [=[myTest7]=]
Test #8: [=[myTest8]=]
Test #9: [=[myTest9]=]
Test #10: [=[myTest10]=]
Test #11: [=[myTest11]=]
Here my code :
find_package(Python COMPONENTS Interpreter Development)
add_test(NAME myTest
COMMAND ${Python_EXECUTABLE} ${CMAKE_CURRENT_SOURCE_DIR}/test.py
WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
)
I don't know how to resolve this issue or how to to disable ctest warnings. I know only disable compilation warnings.

Related

DNNC throws error " terminate called after throwing an instance of 'invalid_random_param' "

I am working on a Xilinx DPU project and was able to train, freeze and quantize my model with the given tools and tensorflow. Now I wanted to use the dnnc-dpu1.4.0 compiler to generate an *.elf file. When executing this command:
dnnc-dpu1.4.0 \
--parser=tensorflow \
--frozen_pb=./quantize_results/deploy_model.pb \
--dpu=1152FA \
--cpu_arch=arm64 \
--output_dir=compile \
--save_kernel \
--mode normal \
--net_name=mnist
it throws this error:
terminate called after throwing an instance of 'invalid_random_param'
what(): Random Param Exception Happened
./compile.sh: line 22: 7602 Aborted (core dumped) dnnc-dpu1.4.0 --parser=tensorflow
--frozen_pb=./quantize_results/deploy_model.pb --dpu=1152FA --cpu_arch=arm64 --output_dir=compile --save_kernel --mode normal --net_name=mnist
I am not sure what to do because this error is very cryptic. It doesn't tell me where those parameters were used or occur, and I won't be able to do something about it. The model works perfectly fine, at least the layers and so on, as I was able to deploy the model itself before. The only thing I changed was the data set and output node count. What could this be? Why is there no extensive error description anywhere?
This is my output for dnnc-dpu1.4.0 --version:
dnnc version v2.05
DPU Target : v1.4.0
Build Label: Jun 24 2019 13:40:08
Copyright #2019 Xilinx Inc. All Rights Reserved.
So I should be up-to-date.
Could anybody help me? This is the last step before I'd be able to deploy my model on the Xilinx DPU. Thank you very much!
Update 1
I posted the same question in the Xilinx Community Forum already.
Update 2
Also, I already found this post on the Xilinx Community Forum, but this does not seem to have a solution to my problem. I can't update the DNNDK, an since I already compiled my model successfully and did no change anything with it, this "solution" seems to be non-applicable to my problem.

Run single test with PhpStorm and PHPUnit on Symfony project fail with error: "Cannot open file"

When I run all tests with PhpStorm everything works fine but when I try to run a single test I get the error:
Cannot open file <namespace>.
We check version of PHP and PHPUnit compatibilities and everything looks fine. When I run single file test the following command is executed:
/php7.4.7/php.exe phpunit-9.4.2.phar --bootstrap <my_project_folder>\tests\bootstrap.php --configuration <my_project_folder>\phpunit.xml.dist --filter "/(::<ClassTestIWantToExecute)( .*)?$/" <namespace_of_classTest> <my_project_folder>\tests\EnsembleImmobilierTest.php --teamcity --cache-result-file=<my_project_folder>\.phpunit.result.cache
PHPUnit is executed but couldn't find the test to execute.

How to fix PyException error in Sikulix 1.1.1?

I am facing the below error in my sikuli script
+++ running this Java
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) Client VM (build 23.21-b01, mixed mode, sharing)
+++ trying to run SikuliX
+++ using: -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine -jar
C:\Users\Administrator\Desktop\UI_testing\Setup\sikulix.jar
[info] HotkeyManager: add Capture Hotkey: CTRL+SHIFT 2 (50, 3)
[info] HotkeyManager: add Abort Hotkey: ALT+SHIFT C (67, 9)
[error] IDE: Remembered window not valid. Going to primary screen
Exception: **org.python.core.PyException thrown from the UncaughtExceptionHandler
in thread "Thread-13"**
Checked and found the code is getting stuck at a line where I used image as a dictionary element
for i in menubar:
exists(menubar[i]).highlight(3)
menubar is a python dictionary which contains images which are stored with their name as key.
PS : code
from sikuli import *
menubar={"file":"menubar_file.png","edit":"menubar_edit.png","view":"menubar_view.png","administration":"menubar_administration.png","tools":"menubar_tools.png","help":"menubar_help.png"}
for i in menubar:
assert exists(menubar[i]).highlight(2)
The assert statement is testing a boolean expression that evaluates to True or False. The Sikuli exists() function however returns a Match object if a pattern found or None in the pattern was not found. You need to rewrite your code accordingly.
Also, I wouldn't use the highlight() like this as it is not clear what it is highlighting.

Sublime Text 3, rbenv, TestUnit, RubyTest and Spring correct configuation to get tests working

So I've setup RubyTest / Sublime Text 3 and that works fine. I'm having trouble getting spring to work in RubyTest. There is this cryptic setting:
"check_for_spring": false,
But when I set to true and run a test it just gives me the default spring command output e.g:
Version: 1.1.3
Usage: spring COMMAND [ARGS]
Commands for spring itself:
If I follow info on this url (https://github.com/rails/spring), correct way to call a test is?
bin/rake test test/functional/posts_controller_test.rb
Now my current settings for test running are:
"run_ruby_unit_command": "ruby -Itest {relative_path}",
"run_single_ruby_unit_command": "ruby -Itest {relative_path} -n '{test_name}'",
If I try chaning to:
bin/rake test
This doesn't work, gives a command not found error even if I copy / paste the command path and it works in shell.
I'm out of ideas help!
This will do the trick
"run_ruby_unit_command": "export PATH=~/.rbenv/shims:$PATH; bin/rake test -Itest {relative_path}",
"run_single_ruby_unit_command": "export PATH=~/.rbenv/shims:$PATH; bin/rake test {relative_path} {test_name}",
I use this
"run_ruby_unit_command": "spring rake test {relative_path}",
"run_single_ruby_unit_command": "spring rake test {relative_path} {test_name}"

junit4 output interpretation

My console output from running JUnit in cmd.exe looks like:
JUnit version 4.10
.....I
Time: 0,469
OK (5 tests)
What does the I on the second line mean?
It means that the test has been #Ignored.