project-chip/connectedhomeip Build error: "ninja: error: unknown target 'python'" - openthread

Cross post to try to find a solution.
https://github.com/project-chip/connectedhomeip/issues/15596
I think I am following the build instructions properly for the Matter configuration app on Pi but it is throwing this error.
Any advice?
pi#otbr:~/connectedhomeip $ scripts/build_python.sh -m platform -d true
Input values: chip_detail_logging = true , chip_mdns = "platform", enable_pybindings = false, chip_case_retry_delta=""
WELCOME TO...
░▓░
▓█▓
▓█▓ ▒█ ▒█
▒██▒▒▓██▒███▒ ░▒▓▒░ ░▒▓▒░ ░░▓█▒░ ░█ █████████████░ ░▒█▒░ ░░▒░
░▓█████▓██░ ▒█▒░░▒▓██▓▒░░▒█▒ ░█▓▒░░▒████ █▓░ █▓░ ▒█▒░░░▒█▓░ ██▒░░
▒█▒░ ░██▒ ░█░ █▓ ░█░ ░▓▒ ░▓█ █▓ █▓ ▒█░░ ░██ ▒▓
░▓██▓░ ░██▓█░ ░█ ▓█ █░ ░█░ ██ █▓ █▓ ▓██████████ ▒█
░▓███▒ ▒███▒░ ░█ ▓█ █░ ██░ ░███ █▓ █▓ ░█▒░ ▒█
░▒████████░ ░███▓▓█▓▓▒ ░█ ▒▒ █░ ░█▓██▓█░▒█ ░▓▓█░ ░▓▓█░ ▒▓▓██▓█░ ▒▓
░██▒░ ▒██▒ ▒██░ ░▒█▓
░▓░ ░▓░
ACTIVATOR! This sets your shell environment variables.
Activating environment (setting environment variables):
Setting environment variables for CIPD package manager...done
Setting environment variables for Python environment.....done
Setting environment variables for pw packages............skipped
Setting environment variables for Host tools.............done
Checking the environment:
20220225 13:09:58 INF Environment passes all checks!
Environment looks good, you are ready to go!
Done. Made 2907 targets from 236 files in 1246ms
ninja: Entering directory `./out/python_lib'
ninja: error: unknown target 'python'

Related

Building Chromium's unit tests: generate_fontconfig_caches failed

I have been able to build Chromium from source, for Ubuntu using this guide.
Subsequently, I want to build the unit tests for it. And specifically, I want to build vaapi_unittest.
I have not been able to do so. First it failed on missing TTF fonts, but after adding a whole bunch of fonts to third_party/test_fonts/test_fonts/ I now get this failure: generate_fontconfig_caches failed with exit code 1
$ autoninja vaapi_unittest
[25/1011] CXX obj/ui/base/x/x/x11_util.o
...
[789/1009] ACTION //third_party/test_fonts/fontconfig:do_generate_fontconfig_caches(//build/toolchain/linux:clang_x64)
FAILED: fontconfig_caches/fb5c91b2895aa445d23aebf7f9e2189c-le64.cache-7
python3 ../../build/gn_run_binary.py generate_fontconfig_caches
generate_fontconfig_caches failed with exit code 1
[802/1009] CXX obj/media/gpu/chromeos/chromeos/video_decoder_pipeline.o
ninja: build stopped: subcommand failed.
How can I avoid this error?
Or alternatively: I'm sure vaapi_unittest does not depend on fonts, so how can I prevent it from depending on that font and its font cache?
This is caused by the following entry in my out/Default/args.gn file:
use_bundled_fontconfig = false
When I set it to true instead, the unit test will compile and link.

IntelliJ Error When Importing Rust Project

I wanted to work on a Rust project and wanted to use IntelliJ and for this I installed Rust plugin:
https://plugins.jetbrains.com/plugin/8182-rust/docs/rust-quick-start.html
I then imported my project in IntelliJ, but somehow I'm not able to see the gutter menu next to my test case. I do not understand what I'm missing. I can see at the bottom in the Build window that there is something that fails.
Updating Workspace Info.
Execution failed (exit code 1).
/home/joesan/.cargo/bin/cargo metadata --verbose --format-version 1 --all-features
stdout : error: no override and no default toolchain set
error: backtrace:
error: 0: error_chain::backtrace::imp::InternalBacktrace::new
1: rustup::config::Cfg::find_or_install_override_toolchain_or_default
2: rustup_init::main
3: std::rt::lang_start_internal::{{closure}}::{{closure}}
at /rustc/c7087fe00d2ba919df1d813c040a5d47e43b0fe7/src/libstd/rt.rs:52
std::sys_common::backtrace::__rust_begin_short_backtrace
at /rustc/c7087fe00d2ba919df1d813c040a5d47e43b0fe7/src/libstd/sys_common/backtrace.rs:130
4: main
5: __libc_start_main
6: <unknown>
stderr :
rustup show gave me the following:
Default host: x86_64-unknown-linux-gnu
rustup home: /opt/softwares/rustup
stable-x86_64-unknown-linux-gnu (default)
rustc 1.46.0 (04488afe3 2020-08-24)
Any ideas how to get this fixed?
I fixed it by opening the Rust project in IntelliJ, navigate to File -> Settings -> Rust and then set the Standard library to the following:
/opt/softwares/rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib
That is the location where I installed the Rust Toolchain. Somehow Intellij was not picking it up and I had to set it manually.

Disable_platform_check configuration setting but getting same error

We are setting up a new DSE 5.1.0 cluster from opscenterd but keep facing this error.
ERROR: Received error from node event-subtype="MeldError" job-id="127e28d3-1b1c-4d63-8f65-f33bb3b100e0" name="Cassandra-4" ssh-management-address="192.168.150.209" node-id="7d946773-13ec-4ca7-9855-0cd032dd4a9b" event-type="error" message="OS platform (CentOS Linux, 7.4.1708, Core) is not supported for DSE 5.1.0. If absolutely necessary, this check can be turned off with the disable_platform_check configuration setting." (opscd-pool-0)
ERROR: Install job 127e28d3-1b1c-4d63-8f65-f33bb3b100e0 failed! (async-thread-macro-11)
INFO: Install job finished for node name="Cassandra-4" ssh-management-address="192.168.150.209" node-id="7d946773-13ec-4ca7-9855-0cd032dd4a9b" (async-thread-macro-10)
Also, we've disabled disable_platform_check and set the value to False (with capital F). But same error.
The flag should be "true". Try adding this line in the opscenter.conf
[lifecycle_manager]
disable_platform_check = True

VSTS build failing with error "Process 'msbuild.exe' exited with code '1'."

Getting that build failed error because I have 4 warnings that read the same.
##[warning]C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\Python Tools\Microsoft.PythonTools.Django.targets(120,5): Warning : Errors while resolving environments: Some project interpreters failed to load:
Interpreter d:\a\1\s\"name of project"\env\ has invalid value for 'Id': env
Interpreter reference has invalid path: Global|PythonCore|3.4
I am using Python 3.4.4 64-bit if that makes a difference.
The build is failing during the Build solution **\*.sln section of the build.
Thank you in advance for any help.
Edit pyproj file to change 10.0 to 15.0
<VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">15.0</VisualStudioVersion>

Robot Framework can't find chromedriver in PATH variable

I want to use Chrome for automation test with Robot Framework. Here are my settings:
*User variables:*
name: webdriver.chrome.driver
value: C:\chromedriver_win32\chromedriver.exe
name: PATH
values: ......;C:\chromedriver_win32\chromedriver.exe
My code:
*** Settings ***
Library BuiltIn
Library Selenium2Library
Library SikuliLibrary
Library OperatingSystem
*** Variables ***
${HOST} = VM
${URL} = http://VM.com
${BROWSER} = Chrome
*** Test Cases ***
Begin Web Test
Open Browser ${URL} ${BROWSER}
maximize browser window
After execution of command: pybot test.robot:
==============================================================================
[ WARN ] Keyword 'Capture Page Screenshot' could not be run on failure: No brows
er is open
Test Case FException
AttributeError: "'Service' object has no attribute 'process'" in <bound method
Service.__del__ of <selenium.webdriver.chrome.service.Service object at 0x000000
0003670278>> ignored
Test Case | FAIL |
Setup failed:
WebDriverException: Message: 'chromedriver' executable needs to be in PATH. Plea
se see https://sites.google.com/a/chromium.org/chromedriver/home
------------------------------------------------------------------------------
What is wrong here?
Thank you
"chromedriver' executable needs to be in PATH" means that the location of chromedriver needs to be in the path. In your case, path needs to be "...;C:\chromedriver_win32". PATH contains folders, not executables.
Download Chromedriver.exe from its official website, extract the .exe file and copy this .exe file in scripts folder of Python installation, e.g. C:\Python36\Scripts
After this, add this scripts path in Environment variable, as below:
and now execute your test case.