Build fails with ROCm on Gentoo Linux

Hi, I have Gentoo Linux with latest updates.
I was fighting with ROCm support and ended up with this package set:
dev-libs/rccl
dev-python/numpy
dev-python/pip
dev-util/roctracer
sci-libs/hipBLAS
sci-libs/hipFFT
sci-libs/hipRAND
sci-libs/hipSOLVER
sci-libs/hipSPARSE
sci-libs/miopen
sys-devel/clang
sys-devel/gcc

with following USE flags for gcc:
 * Found these USE flags for sys-devel/gcc-13.2.1_p20240210:
 U I
 - - ada                            : Build the ADA language (GNAT) frontend
 - - cet                            : (Restricted to >=sys-devel/gcc-10)
                                      Enable support for control flow hijacking protection. On amd64, this provides Intel
                                      Control Flow Enforcement Technology (CET). On arm64, this provides Branch Target
                                      Identification (BTI) and Pointer Authentication Code (PAC) support. This is only effective
                                      on amd64 or arm64. Only provides benefits on newer CPUs. For Intel, the CPU must be at
                                      least as new as Tiger Lake. For AMD, it must be at least as new as Zen 3. This is harmless
                                      on older CPUs, but provides no benefit either. For ARM64, PAC was introduced in armv8.3-a,
                                      and BTI was introduced in armv8.5-a. When combined with USE=hardened on amd64, GCC will
                                      set -fcf-protection by default when building software. The effect is minimal on systems
                                      which do not support it, other than a possible small increase in codesize for the NOPs.
                                      The generated code is therefore compatible with i686 at the earliest. On arm64, GCC will
                                      set -mbranch-protection=standard by default when building software.
 - - d                              : Enable support for the D programming language
 - - debug                          : Enables GCC's 'checking' facility via --enable-checking=yes,extra,rtl. This adds checks to
                                      various compiler passes for integrity and input validation. This can help catch possible
                                      miscompilations early as well as latent bugs which could become real problems in future,
                                      but at the cost of slower compile times when using GCC. Unrelated to backtraces.
 - - default-stack-clash-protection : Build packages with stack clash protection on by default as a hardening measure. This
                                      enables -fstack-clash-protection by default which protects against large memory
                                      allocations allowing stack smashing. May cause slightly increased codesize, but modern
                                      compilers have been adapted to optimize well for this case, as this mitigation is now
                                      quite common. See
                                      https://developers.redhat.com/blog/2020/05/22/stack-clash-mitigation-in-gcc-part-3 and
                                      https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt.
 - - default-znow                   : Request full relocation on start from ld.so by default. This sets the -z,now (BIND_NOW)
                                      flag by default on all linker invocations. By resolving all dynamic symbols at application
                                      startup, parts of the program can be made read-only as a hardening measure. This is
                                      closely related to RELRO which is also separately enabled by default. In some applications
                                      with many unresolved symbols (heavily plugin based, for example), startup time may be
                                      impacted.
 - - doc                            : Add extra documentation (API, Javadoc, etc). It is recommended to enable per package
                                      instead of globally
 + + fortran                        : Add support for fortran
 - - go                             : Build the GCC Go language frontend.
 - - graphite                       : Add support for the framework for loop optimizations based on a polyhedral intermediate
                                      representation
 - - hardened                       : Activate default security enhancements for toolchain (gcc, glibc, binutils)
 - - jit                            : Enable libgccjit so other applications can embed gcc for Just-In-Time compilation.
 - - lto                            : Build using Link Time Optimizations (LTO). Note that GCC is always built with support for
                                      building other programs with LTO. This USE flag is for whether GCC itself is built and
                                      optimized with LTO.
 - - modula2                        : Build the GCC Modula-2 language frontend.
 + + nls                            : Add Native Language Support (using gettext - GNU locale utilities)
 + + objc                           : Build support for the Objective C code language
 + + objc++                         : Build support for the Objective C++ language
 - - objc-gc                        : Build support for the Objective C code language Garbage Collector
 + + openmp                         : Build support for the OpenMP (support parallel computing), requires >=sys-devel/gcc-4.2
                                      built with USE="openmp"
 - - pgo                            : Build GCC using Profile Guided Optimization (PGO). GCC will build itself and then analyze
                                      the just-built binary and then rebuild itself using the data obtained from analysis of
                                      codepaths taken. It does not affect whether GCC itself supports PGO when building other
                                      software. This substantially increases the build time needed for building GCC itself.
 + + sanitize                       : Build support for various sanitizer functions (ASAN/TSAN/etc...) to find runtime problems
                                      in applications.
 + + ssp                            : Build packages with stack smashing protection on by default
 - - systemtap                      : enable systemtap static probe points
 - - test                           : Enable dependencies and/or preparations necessary to run tests (usually controlled by
                                      FEATURES=test but can be toggled independently)
 - - valgrind                       : Enable annotations for accuracy. May slow down runtime slightly. Safe to use even if not
                                      currently using dev-debug/valgrind
 - - vanilla                        : Do not add extra patches which change default behaviour; DO NOT USE THIS ON A GLOBAL SCALE
                                      as the severity of the meaning changes drastically
 - - vtv                            : Build support for virtual table verification (a C++ hardening feature). This does not
                                      control whether GCC defaults to using VTV> Note that actually using VTV breaks ABI and
                                      hence the whole system must be built with -fvtable-verify.
 - - zstd                           : Enable support for ZSTD compression

and such environment variables:
export EXLA_TARGET="rocm"
export ROCM_PATH="/usr"
export XLA_BUILD="true"
export XLA_TARGET="rocm"

Regardless of what I should and can install there are lots of weird problems:

TF_ROCM_AMDGPU_TARGETS is set in code without a way to change it and is set to: "gfx900,gfx906,gfx908,gfx90a,gfx1030". Not only this builds support for many GPUs which rarely is important, but also I need to edit xla source code to support new cards (my uses gfx1100)

rocm_configure.bzl only in theory supports ROCM_PATH which is not /opt/rocm or /opt/rocm-version. In practice it forces some paths to be within hip and roctracer sub-directories which is not a case for installing ROCm packages in /usr like: /usr/lib64/libamdhip64.so. The file tries few path versions which is nice as long as it does not assumes putting a sub-directory. I would not be surprised if such sub-directory would have each case, but it's about 2 of 12 libs

xla does not specify a dependencies list - reading all of that error messages and not ending up with a working setup is truly exhausting :face_exhaling:

The only know success builds are using old gcc versions which is a serious problem on prod machines

You may have issues with newer and older versions of GCC. XLA builds are known to work with GCC versions between 7.5 and 9.3.

meanwhile emerge command returns:
# emerge -pv sys-devel/gcc:9.5.0

These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 0.80 s (backtrack: 0/20).

!!! All ebuilds that could satisfy "sys-devel/gcc:9.5.0" have been masked.
!!! One of the following masked packages is required to complete your request:
- sys-devel/gcc-9.5.0::gentoo (masked by: package.mask)
/var/db/repos/gentoo/profiles/package.mask:
# Sam James<EMAIL_ADDRESS>(2023-11-19)
# GCC 10 and older no longer receive upstream support or fixes for
# bugs. Please switch to a newer GCC version using gcc-config.
# The lowest supported version of GCC is GCC 11.

For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

Of course nobody expects support of a 14.0.1_pre* releases of GCC, but requiring at most 5 versions major versions back excluding even latest updates for 9.x branch is a critical issue for a prod machines.
Anyway, I have tried to use GCC version 8.5 as well as 13.2.1  with clang version 16 and 17, but none of them compiled successfully.
Firstly the logs before fixing rocm_configure.bzl:
$ mix compile
==> earmark_parser
Compiling 2 files (.xrl)
Compiling 1 file (.yrl)
Compiling 3 files (.erl)
Compiling 46 files (.ex)
Generated earmark_parser app
==> nimble_parsec
Compiling 4 files (.ex)
Generated nimble_parsec app
==> makeup
Compiling 15 files (.ex)
Generated makeup app
==> makeup_elixir
Compiling 6 files (.ex)
Generated makeup_elixir app
==> makeup_erlang
Compiling 4 files (.ex)
Generated makeup_erlang app
==> ex_doc
Compiling 26 files (.ex)
Generated ex_doc app
==> elixir_make
Compiling 6 files (.ex)
Generated elixir_make app
==> xla
Compiling 2 files (.ex)
Generated xla app
mkdir -p $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb && \
        cd $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb && \
        git init && \
        git remote add origin https://github.com/openxla/xla.git && \
        git fetch --depth 1 origin 771e38178340cbaaef8ff20f44da5407c15092cb && \
        git checkout FETCH_HEAD && \
        rm $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelversion
Zainicjowano puste repozytorium Gita w $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.git/
Z https://github.com/openxla/xla
 * branch            771e38178340cbaaef8ff20f44da5407c15092cb -> FETCH_HEAD
Uwaga: przełączanie na „FETCH_HEAD”.

Jesteś w stanie „odłączonego HEAD”. Możesz się rozglądać, tworzyć
eksperymentalne zmiany i je składać, i możesz odrzucić wszystkie zapisy,
które złożysz w tym stanie, bez wpływu na żadną gałąź, przełączając z powrotem na jakąś gałąź.

Jeśli chcesz utworzyć nową gałąź, która zachowa zapisy, które złożysz,
możesz to zrobić (teraz lub później) używając -c w ponownym poleceniu przełączenia.

Starting local Bazel server and connecting to it...
INFO: Reading 'startup' options from $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --windows_enable_symlinks
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=0 --terminal_columns=80
INFO: Reading rc options for 'build' from $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc:
  'build' options: --define framework_shared_object=true --define tsl_protobuf_header_only=true --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --features=-force_no_whole_archive --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2 --define=no_aws_support=true --define=no_hdfs_support=true --experimental_cc_shared_library --experimental_link_static_libraries_once=false --incompatible_enforce_config_setting_visibility
INFO: Found applicable config definition build:short_logs in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:rocm in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --crosstool_top=@local_config_rocm//crosstool:toolchain --define=using_rocm_hipcc=true --define=tensorflow_mkldnn_contraction_kernel=0 --repo_env TF_NEED_ROCM=1 --config=no_tfrt
INFO: Found applicable config definition build:no_tfrt in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --deleted_packages=tensorflow/compiler/mlir/tfrt,tensorflow/compiler/mlir/tfrt/benchmarks,tensorflow/compiler/mlir/tfrt/ir,tensorflow/compiler/mlir/tfrt/ir/mlrt,tensorflow/compiler/mlir/tfrt/jit/python_binding,tensorflow/compiler/mlir/tfrt/jit/transforms,tensorflow/compiler/mlir/tfrt/python_tests,tensorflow/compiler/mlir/tfrt/tests,tensorflow/compiler/mlir/tfrt/tests/ifrt,tensorflow/compiler/mlir/tfrt/tests/mlrt,tensorflow/compiler/mlir/tfrt/tests/ir,tensorflow/compiler/mlir/tfrt/tests/analysis,tensorflow/compiler/mlir/tfrt/tests/jit,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_tfrt,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_jitrt,tensorflow/compiler/mlir/tfrt/tests/tf_to_corert,tensorflow/compiler/mlir/tfrt/tests/tf_to_tfrt_data,tensorflow/compiler/mlir/tfrt/tests/saved_model,tensorflow/compiler/mlir/tfrt/transforms/lhlo_gpu_to_tfrt_gpu,tensorflow/compiler/mlir/tfrt/transforms/mlrt,tensorflow/core/runtime_fallback,tensorflow/core/runtime_fallback/conversion,tensorflow/core/runtime_fallback/kernel,tensorflow/core/runtime_fallback/opdefs,tensorflow/core/runtime_fallback/runtime,tensorflow/core/runtime_fallback/util,tensorflow/core/runtime_fallback/test,tensorflow/core/runtime_fallback/test/gpu,tensorflow/core/runtime_fallback/test/saved_model,tensorflow/core/runtime_fallback/test/testdata,tensorflow/core/tfrt/stubs,tensorflow/core/tfrt/tfrt_session,tensorflow/core/tfrt/mlrt,tensorflow/core/tfrt/mlrt/attribute,tensorflow/core/tfrt/mlrt/kernel,tensorflow/core/tfrt/mlrt/bytecode,tensorflow/core/tfrt/mlrt/interpreter,tensorflow/compiler/mlir/tfrt/translate/mlrt,tensorflow/compiler/mlir/tfrt/translate/mlrt/testdata,tensorflow/core/tfrt/gpu,tensorflow/core/tfrt/run_handler_thread_pool,tensorflow/core/tfrt/runtime,tensorflow/core/tfrt/saved_model,tensorflow/core/tfrt/graph_executor,tensorflow/core/tfrt/saved_model/tests,tensorflow/core/tfrt/tpu,tensorflow/core/tfrt/utils,tensorflow/core/tfrt/utils/debug,tensorflow/core/tfrt/saved_model/python,tensorflow/core/tfrt/graph_executor/python,tensorflow/core/tfrt/saved_model/utils
INFO: Found applicable config definition build:linux in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --host_copt=-w --copt=-Wno-all --copt=-Wno-extra --copt=-Wno-deprecated --copt=-Wno-deprecated-declarations --copt=-Wno-ignored-attributes --copt=-Wno-array-bounds --copt=-Wunused-result --copt=-Werror=unused-result --copt=-Wswitch --copt=-Werror=switch --copt=-Wno-error=unused-but-set-variable --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++17 --host_cxxopt=-std=c++17 --config=dynamic_kernels --experimental_guard_against_concurrent_changes
INFO: Found applicable config definition build:dynamic_kernels in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
Loading:
DEBUG: $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'llvm-raw' because it already exists.
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading:
Loading: 0 packages loaded
INFO: Repository local_config_rocm instantiated at:
  $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/WORKSPACE:19:15: in <toplevel>
  $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/workspace2.bzl:90:19: in workspace
  $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/workspace2.bzl:626:19: in workspace
  $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/workspace2.bzl:80:19: in _tf_toolchains
Repository rule rocm_configure defined at:
  $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl:832:33: in <toplevel>
ERROR: An error occurred during the fetch of repository 'local_config_rocm':
   Traceback (most recent call last):
        File "$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl", line 810, column 38, in _rocm_autoconf_impl
                _create_local_rocm_repository(repository_ctx)
        File "$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl", line 599, column 27, in _create_local_rocm_repository
                rocm_libs = _find_libs(repository_ctx, rocm_config, hipfft_or_rocfft, miopen_path, rccl_path, bash_bin)
        File "$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl", line 366, column 34, in _find_libs
                return _select_rocm_lib_paths(repository_ctx, libs_paths, bash_bin)
        File "$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl", line 328, column 36, in _select_rocm_lib_paths
                auto_configure_fail("Cannot find rocm library %s" % name)
        File "$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl", line 153, column 9, in auto_configure_fail
                fail("\n%sROCm Configuration Error:%s %s\n" % (red, no_color, msg))
Error in fail:
ROCm Configuration Error: Cannot find rocm library amdhip64
ERROR: $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/WORKSPACE:19:15: fetching rocm_configure rule //external:local_config_rocm: Traceback (most recent call last):
        File "$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl", line 810, column 38, in _rocm_autoconf_impl
                _create_local_rocm_repository(repository_ctx)
        File "$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl", line 599, column 27, in _create_local_rocm_repository
                rocm_libs = _find_libs(repository_ctx, rocm_config, hipfft_or_rocfft, miopen_path, rccl_path, bash_bin)
        File "$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl", line 366, column 34, in _find_libs
                return _select_rocm_lib_paths(repository_ctx, libs_paths, bash_bin)
        File "$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl", line 328, column 36, in _select_rocm_lib_paths
                auto_configure_fail("Cannot find rocm library %s" % name)
        File "$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/tsl/third_party/gpus/rocm_configure.bzl", line 153, column 9, in auto_configure_fail
                fail("\n%sROCm Configuration Error:%s %s\n" % (red, no_color, msg))
Error in fail:
ROCm Configuration Error: Cannot find rocm library amdhip64
ERROR: Skipping '//xla/extension:xla_extension': no such package '@local_config_rocm//rocm':
ROCm Configuration Error: Cannot find rocm library amdhip64
WARNING: Target pattern parsing failed.
ERROR: no such package '@local_config_rocm//rocm':
ROCm Configuration Error: Cannot find rocm library amdhip64
INFO: Elapsed time: 34.221s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
make: *** [Makefile:26: $HOME/.cache/xla/0.6.0/cache/build/xla_extension-x86_64-linux-gnu-rocm.tar.gz] Błąd 1
** (Mix) Could not compile with "make" (exit status: 2).
You need to have gcc and make installed. If you are using
Ubuntu or any other Debian-based system, install the packages
"build-essential". Also install "erlang-dev" package if not
included in your Erlang/OTP version. If you're on Fedora, run
"dnf group install 'Development Tools'".

After mentioned fix:
$ mix compile
rm -f $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/xla/extension && \
        ln -s "$HOME/xla/extension" $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/xla/extension && \
        cd $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb && \
        bazel build --define "framework_shared_object=false" -c opt   --config=rocm --action_env=HIP_PLATFORM=amd --action_env=TF_ROCM_AMDGPU_TARGETS="gfx1100" //xla/extension:xla_extension && \
        mkdir -p $HOME/.cache/xla/0.6.0/cache/build/ && \
        cp -f $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/bazel-bin/xla/extension/xla_extension.tar.gz $HOME/.cache/xla/0.6.0/cache/build/xla_extension-x86_64-linux-gnu-rocm.tar.gz
INFO: Reading 'startup' options from $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --windows_enable_symlinks
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=0 --terminal_columns=80
INFO: Reading rc options for 'build' from $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc:
  'build' options: --define framework_shared_object=true --define tsl_protobuf_header_only=true --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --features=-force_no_whole_archive --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2 --define=no_aws_support=true --define=no_hdfs_support=true --experimental_cc_shared_library --experimental_link_static_libraries_once=false --incompatible_enforce_config_setting_visibility
INFO: Found applicable config definition build:short_logs in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:rocm in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --crosstool_top=@local_config_rocm//crosstool:toolchain --define=using_rocm_hipcc=true --define=tensorflow_mkldnn_contraction_kernel=0 --repo_env TF_NEED_ROCM=1 --config=no_tfrt
INFO: Found applicable config definition build:no_tfrt in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --deleted_packages=tensorflow/compiler/mlir/tfrt,tensorflow/compiler/mlir/tfrt/benchmarks,tensorflow/compiler/mlir/tfrt/ir,tensorflow/compiler/mlir/tfrt/ir/mlrt,tensorflow/compiler/mlir/tfrt/jit/python_binding,tensorflow/compiler/mlir/tfrt/jit/transforms,tensorflow/compiler/mlir/tfrt/python_tests,tensorflow/compiler/mlir/tfrt/tests,tensorflow/compiler/mlir/tfrt/tests/ifrt,tensorflow/compiler/mlir/tfrt/tests/mlrt,tensorflow/compiler/mlir/tfrt/tests/ir,tensorflow/compiler/mlir/tfrt/tests/analysis,tensorflow/compiler/mlir/tfrt/tests/jit,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_tfrt,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_jitrt,tensorflow/compiler/mlir/tfrt/tests/tf_to_corert,tensorflow/compiler/mlir/tfrt/tests/tf_to_tfrt_data,tensorflow/compiler/mlir/tfrt/tests/saved_model,tensorflow/compiler/mlir/tfrt/transforms/lhlo_gpu_to_tfrt_gpu,tensorflow/compiler/mlir/tfrt/transforms/mlrt,tensorflow/core/runtime_fallback,tensorflow/core/runtime_fallback/conversion,tensorflow/core/runtime_fallback/kernel,tensorflow/core/runtime_fallback/opdefs,tensorflow/core/runtime_fallback/runtime,tensorflow/core/runtime_fallback/util,tensorflow/core/runtime_fallback/test,tensorflow/core/runtime_fallback/test/gpu,tensorflow/core/runtime_fallback/test/saved_model,tensorflow/core/runtime_fallback/test/testdata,tensorflow/core/tfrt/stubs,tensorflow/core/tfrt/tfrt_session,tensorflow/core/tfrt/mlrt,tensorflow/core/tfrt/mlrt/attribute,tensorflow/core/tfrt/mlrt/kernel,tensorflow/core/tfrt/mlrt/bytecode,tensorflow/core/tfrt/mlrt/interpreter,tensorflow/compiler/mlir/tfrt/translate/mlrt,tensorflow/compiler/mlir/tfrt/translate/mlrt/testdata,tensorflow/core/tfrt/gpu,tensorflow/core/tfrt/run_handler_thread_pool,tensorflow/core/tfrt/runtime,tensorflow/core/tfrt/saved_model,tensorflow/core/tfrt/graph_executor,tensorflow/core/tfrt/saved_model/tests,tensorflow/core/tfrt/tpu,tensorflow/core/tfrt/utils,tensorflow/core/tfrt/utils/debug,tensorflow/core/tfrt/saved_model/python,tensorflow/core/tfrt/graph_executor/python,tensorflow/core/tfrt/saved_model/utils
INFO: Found applicable config definition build:linux in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --host_copt=-w --copt=-Wno-all --copt=-Wno-extra --copt=-Wno-deprecated --copt=-Wno-deprecated-declarations --copt=-Wno-ignored-attributes --copt=-Wno-array-bounds --copt=-Wunused-result --copt=-Werror=unused-result --copt=-Wswitch --copt=-Werror=switch --copt=-Wno-error=unused-but-set-variable --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++17 --host_cxxopt=-std=c++17 --config=dynamic_kernels --experimental_guard_against_concurrent_changes
INFO: Found applicable config definition build:dynamic_kernels in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
Loading:
Loading:
Loading: 0 packages loaded
Analyzing: target //xla/extension:xla_extension (1 packages loaded, 0 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (35 packages loaded, 14 targets configured)
Analyzing: target //xla/extension:xla_extension (68 packages loaded, 217 targets configured)
Analyzing: target //xla/extension:xla_extension (163 packages loaded, 11268 targets configured)
Analyzing: target //xla/extension:xla_extension (165 packages loaded, 11806 targets configured)
Analyzing: target //xla/extension:xla_extension (178 packages loaded, 12976 targets configured)
Analyzing: target //xla/extension:xla_extension (179 packages loaded, 13496 targets configured)
Analyzing: target //xla/extension:xla_extension (179 packages loaded, 13496 targets configured)
Analyzing: target //xla/extension:xla_extension (180 packages loaded, 14375 targets configured)
Analyzing: target //xla/extension:xla_extension (181 packages loaded, 15160 targets configured)
Analyzing: target //xla/extension:xla_extension (181 packages loaded, 15160 targets configured)
Analyzing: target //xla/extension:xla_extension (181 packages loaded, 15160 targets configured)
INFO: Analyzed target //xla/extension:xla_extension (182 packages loaded, 15807 targets configured).
INFO: Found 1 target...
[0 / 71] [Prepa] BazelWorkspaceStatusAction stable-status.txt ... (3 actions, 2 running)
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/llvm-project/llvm/BUILD.bazel:191:11: Compiling llvm/lib/Demangle/Demangle.cpp [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @llvm-project//llvm:Demangle) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 76 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1plus’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling gzwrite.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling inftrees.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/llvm-project/llvm/BUILD.bazel:191:11: Compiling llvm/lib/Demangle/RustDemangle.cpp [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @llvm-project//llvm:Demangle) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 76 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1plus’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling inflate.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling inffast.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling adler32.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling trees.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling crc32.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling deflate.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling zutil.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling gzclose.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling infback.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling compress.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling gzlib.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/zlib/BUILD.bazel:5:11: Compiling uncompr.c [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @zlib//:zlib) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 37 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
gcc: fatal error: cannot execute ‘cc1’: execvp: No such file or directory
compilation terminated.
Target //xla/extension:xla_extension failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/llvm-project/mlir/BUILD.bazel:9224:10 Middleman _middlemen/@llvm-project_S_Smlir_Cmlir-tblgen-BazelCppSemantics_build_arch_k8-opt-exec-50AE0418 failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @llvm-project//llvm:Demangle) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 76 arguments skipped)
INFO: Elapsed time: 29.007s, Critical Path: 0.09s
INFO: 65 processes: 63 internal, 2 local.
FAILED: Build did NOT complete successfully
make: *** [Makefile:26: $HOME/.cache/xla/0.6.0/cache/build/xla_extension-x86_64-linux-gnu-rocm.tar.gz] Błąd 1
** (Mix) Could not compile with "make" (exit status: 2).
You need to have gcc and make installed. If you are using
Ubuntu or any other Debian-based system, install the packages
"build-essential". Also install "erlang-dev" package if not
included in your Erlang/OTP version. If you're on Fedora, run
"dnf group install 'Development Tools'".

Somehow it does not detects properly the gcc. Surprisingly by default it's specific location is not in the PATH variable:
# same with 9.5.0 version
export PATH="$PATH:/usr/libexec/gcc/x86_64-pc-linux-gnu/13/"

The final result is:
$ mix compile
rm -f $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/xla/extension && \
        ln -s "$HOME/xla/extension" $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/xla/extension && \
        cd $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb && \
        bazel build --define "framework_shared_object=false" -c opt   --config=rocm --action_env=HIP_PLATFORM=amd --action_env=TF_ROCM_AMDGPU_TARGETS="gfx1100" //xla/extension:xla_extension && \
        mkdir -p $HOME/.cache/xla/0.6.0/cache/build/ && \
        cp -f $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/bazel-bin/xla/extension/xla_extension.tar.gz $HOME/.cache/xla/0.6.0/cache/build/xla_extension-x86_64-linux-gnu-rocm.tar.gz
INFO: Reading 'startup' options from $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --windows_enable_symlinks
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=0 --terminal_columns=80
INFO: Reading rc options for 'build' from $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc:
  'build' options: --define framework_shared_object=true --define tsl_protobuf_header_only=true --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --features=-force_no_whole_archive --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2 --define=no_aws_support=true --define=no_hdfs_support=true --experimental_cc_shared_library --experimental_link_static_libraries_once=false --incompatible_enforce_config_setting_visibility
INFO: Found applicable config definition build:short_logs in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:rocm in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --crosstool_top=@local_config_rocm//crosstool:toolchain --define=using_rocm_hipcc=true --define=tensorflow_mkldnn_contraction_kernel=0 --repo_env TF_NEED_ROCM=1 --config=no_tfrt
INFO: Found applicable config definition build:no_tfrt in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --deleted_packages=tensorflow/compiler/mlir/tfrt,tensorflow/compiler/mlir/tfrt/benchmarks,tensorflow/compiler/mlir/tfrt/ir,tensorflow/compiler/mlir/tfrt/ir/mlrt,tensorflow/compiler/mlir/tfrt/jit/python_binding,tensorflow/compiler/mlir/tfrt/jit/transforms,tensorflow/compiler/mlir/tfrt/python_tests,tensorflow/compiler/mlir/tfrt/tests,tensorflow/compiler/mlir/tfrt/tests/ifrt,tensorflow/compiler/mlir/tfrt/tests/mlrt,tensorflow/compiler/mlir/tfrt/tests/ir,tensorflow/compiler/mlir/tfrt/tests/analysis,tensorflow/compiler/mlir/tfrt/tests/jit,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_tfrt,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_jitrt,tensorflow/compiler/mlir/tfrt/tests/tf_to_corert,tensorflow/compiler/mlir/tfrt/tests/tf_to_tfrt_data,tensorflow/compiler/mlir/tfrt/tests/saved_model,tensorflow/compiler/mlir/tfrt/transforms/lhlo_gpu_to_tfrt_gpu,tensorflow/compiler/mlir/tfrt/transforms/mlrt,tensorflow/core/runtime_fallback,tensorflow/core/runtime_fallback/conversion,tensorflow/core/runtime_fallback/kernel,tensorflow/core/runtime_fallback/opdefs,tensorflow/core/runtime_fallback/runtime,tensorflow/core/runtime_fallback/util,tensorflow/core/runtime_fallback/test,tensorflow/core/runtime_fallback/test/gpu,tensorflow/core/runtime_fallback/test/saved_model,tensorflow/core/runtime_fallback/test/testdata,tensorflow/core/tfrt/stubs,tensorflow/core/tfrt/tfrt_session,tensorflow/core/tfrt/mlrt,tensorflow/core/tfrt/mlrt/attribute,tensorflow/core/tfrt/mlrt/kernel,tensorflow/core/tfrt/mlrt/bytecode,tensorflow/core/tfrt/mlrt/interpreter,tensorflow/compiler/mlir/tfrt/translate/mlrt,tensorflow/compiler/mlir/tfrt/translate/mlrt/testdata,tensorflow/core/tfrt/gpu,tensorflow/core/tfrt/run_handler_thread_pool,tensorflow/core/tfrt/runtime,tensorflow/core/tfrt/saved_model,tensorflow/core/tfrt/graph_executor,tensorflow/core/tfrt/saved_model/tests,tensorflow/core/tfrt/tpu,tensorflow/core/tfrt/utils,tensorflow/core/tfrt/utils/debug,tensorflow/core/tfrt/saved_model/python,tensorflow/core/tfrt/graph_executor/python,tensorflow/core/tfrt/saved_model/utils
INFO: Found applicable config definition build:linux in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --host_copt=-w --copt=-Wno-all --copt=-Wno-extra --copt=-Wno-deprecated --copt=-Wno-deprecated-declarations --copt=-Wno-ignored-attributes --copt=-Wno-array-bounds --copt=-Wunused-result --copt=-Werror=unused-result --copt=-Wswitch --copt=-Werror=switch --copt=-Wno-error=unused-but-set-variable --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include --define=PROTOBUF_INCLUDE_PATH=$(PREFIX)/include --cxxopt=-std=c++17 --host_cxxopt=-std=c++17 --config=dynamic_kernels --experimental_guard_against_concurrent_changes
INFO: Found applicable config definition build:dynamic_kernels in file $HOME/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/.bazelrc: --define=dynamic_loaded_kernels=true --copt=-DAUTOLOAD_DYNAMIC_KERNELS
Loading:
Loading:
Loading: 0 packages loaded
Analyzing: target //xla/extension:xla_extension (0 packages loaded, 0 targets configured)
INFO: Analyzed target //xla/extension:xla_extension (1 packages loaded, 2 targets configured).
INFO: Found 1 target...
[0 / 4] [Prepa] BazelWorkspaceStatusAction stable-status.txt
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/llvm-project/llvm/BUILD.bazel:191:11: Compiling llvm/lib/Demangle/MicrosoftDemangleNodes.cpp [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @llvm-project//llvm:Demangle) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 76 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
In file included from external/llvm-project/llvm/lib/Demangle/MicrosoftDemangleNodes.cpp:13:
external/llvm-project/llvm/include/llvm/Demangle/MicrosoftDemangleNodes.h:16:10: fatal error: array: No such file or directory
   16 | #include <array>
      |          ^~~~~~~
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/llvm-project/llvm/BUILD.bazel:360:11: Compiling llvm/lib/TableGen/Parser.cpp [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @llvm-project//llvm:TableGen) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 81 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
In file included from external/llvm-project/llvm/include/llvm/ADT/STLExtras.h:20,
                 from external/llvm-project/llvm/include/llvm/TableGen/Parser.h:16,
                 from external/llvm-project/llvm/lib/TableGen/Parser.cpp:9:
external/llvm-project/llvm/include/llvm/ADT/ADL.h:12:10: fatal error: type_traits: No such file or directory
   12 | #include <type_traits>
      |          ^~~~~~~~~~~~~
compilation terminated.
ERROR: $HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/external/llvm-project/llvm/BUILD.bazel:191:11: Compiling llvm/lib/Demangle/RustDemangle.cpp [for tool] failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target @llvm-project//llvm:Demangle) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 76 arguments skipped)
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:159: SyntaxWarning: invalid escape sequence '\.'
  re.search('\.cpp$|\.cc$|\.c$|\.cxx$|\.C$', f)]
$HOME/.cache/bazel/_bazel_eiji/24d5313c51521fe9b48548641c43cdae/execroot/xla/external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc:23: DeprecationWarning: 'pipes' is deprecated and slated for removal in Python 3.13
  import pipes
In file included from external/llvm-project/llvm/lib/Demangle/RustDemangle.cpp:14:
external/llvm-project/llvm/include/llvm/Demangle/Demangle.h:12:10: fatal error: cstddef: No such file or directory
   12 | #include <cstddef>
      |          ^~~~~~~~~
compilation terminated.
Target //xla/extension:xla_extension failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 0.269s, Critical Path: 0.07s
INFO: 47 processes: 44 internal, 3 local.
FAILED: Build did NOT complete successfully
make: *** [Makefile:26: $HOME/.cache/xla/0.6.0/cache/build/xla_extension-x86_64-linux-gnu-rocm.tar.gz] Błąd 1
** (Mix) Could not compile with "make" (exit status: 2).
You need to have gcc and make installed. If you are using
Ubuntu or any other Debian-based system, install the packages
"build-essential". Also install "erlang-dev" package if not
included in your Erlang/OTP version. If you're on Fedora, run
"dnf group install 'Development Tools'".

However the header files already existing within gcc installation: /usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13. What have surprised me is lots of Loding: lines without any other information. In last build attempt the number of such lines decreased to just 2. Maybe I still don't have 2 things found or installed?
So far I was unmasking unsupported packages, compilling few configurations of gcc and clang and even editing source files. I'm a bit tired today and it would be a big relief if somebody could help me with this environment setup. Have I missed something? Are new AMD GPUs even supported? Or maybe there are other problems in source files? Maybe should I try some unreleased branches?
Here are some information about my setup:
$ asdf current
bazel           6.1.2           $HOME/.tool-versions
elixir          ref:v1.16.2     $HOME/.tool-versions
erlang          26.2.3          $HOME/.tool-versions
imagemagick     7.1.1-29        $HOME/.tool-versions
java            temurin-21.0.2+13.0.LTS $HOME/.tool-versions
nodejs          21.6.2          $HOME/.tool-versions
php             8.3.4           $HOME/.tool-versions
postgres        16.2            $HOME/.tool-versions
ruby            3.3.0           $HOME/.tool-versions
rust            1.76.0          $HOME/.tool-versions
sqlite          3.45.2          $HOME/.tool-versions

There are other issues about compiling ROCm which you can investigate. Unfortunately, those issues are really coming from Bazel, so there may not be much we can do from this project.

@josevalim For now I don't have any ideas, but I can work on my setup if you have some. I saw that not much people use ROCm here, so I can do testing if you could guide me what can I do now.

Yeah, it's really Bazel and XLA. ROCm is definitely not as prioritized and widely used, so there seem to be more issues with getting the build environment right. I would try building the binary within Docker, see https://github.com/elixir-nx/xla/issues/63#issuecomment-1817744344.

@jonatanklosko may I ask how are you able to build the binary in docker?
I am trying to reproduce it in Linux machine using the provided Dockerfile and I get a ton of errors, I am able to solve some, but I reach a point where it seems I need to start modifying code in the libraries not only in the environment.

@jalberto interesting, the build itself doesn't require an actual GPU, so the Docker build should be reproducible. What kind of errors are you getting?

@jonatanklosko I tried in a clean env, with a new clone of the repo and use build/build.sh rocm:
1st error, easy to solve:
[2/2] STEP 19/21: COPY Makefile Makefile.win ./
Error: building at STEP "COPY Makefile Makefile.win ./": checking on sources under "/home/ja/Projects/Misc/tmp/xla": copier: stat: "/Makefile.win": no such file or directory

after that fix, we are in the correct path: Successfully tagged localhost/xla-rocm:latest
After a while:
[1,954 / 6,477] Compiling xla/service/gpu/runtime3/custom_call_thunk.cc; 4s local ... (16 actions, 15 running)
ERROR: /root/.cache/xla_extension/xla-771e38178340cbaaef8ff20f44da5407c15092cb/xla/service/gpu/BUILD:1158:23: Compiling xla/service/gpu/cub_sort_kernel.cu.cc failed: (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command (from target //xla/service/gpu:cub_sort_kernel_f64) external/local_config_rocm/crosstool/clang/bin/crosstool_wrapper_driver_is_not_gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer ... (remaining 100 arguments skipped)
Warning: HIP_PLATFORM=hcc is deprecated. Please use HIP_PLATFORM=amd.
clang++: warning: argument unused during compilation: '-fcuda-flush-denormals-to-zero' [-Wunused-command-line-argument]
Warning: HIP_PLATFORM=hcc is deprecated. Please use HIP_PLATFORM=amd.
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr43 = V_MOV_B32_dpp undef $vgpr43(tied-def 0), $vgpr4, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr4 = V_MOV_B32_dpp undef $vgpr4(tied-def 0), killed $vgpr3, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr3 = V_MOV_B32_dpp undef $vgpr3(tied-def 0), $vgpr2, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr47 = V_MOV_B32_dpp undef $vgpr47(tied-def 0), $vgpr45, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr44 = V_MOV_B32_dpp undef $vgpr44(tied-def 0), $vgpr43, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr47 = V_MOV_B32_dpp undef $vgpr47(tied-def 0), $vgpr45, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr44 = V_MOV_B32_dpp undef $vgpr44(tied-def 0), $vgpr43, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr43 = V_MOV_B32_dpp undef $vgpr43(tied-def 0), $vgpr4, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr47 = V_MOV_B32_dpp undef $vgpr47(tied-def 0), $vgpr45, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr44 = V_MOV_B32_dpp undef $vgpr44(tied-def 0), $vgpr43, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr47 = V_MOV_B32_dpp undef $vgpr47(tied-def 0), $vgpr45, 322, 15, 15, 0, implicit $exec
error: Illegal instruction detected: Invalid dpp_ctrl value: broadcasts are not supported on GFX10+
renamable $vgpr44 = V_MOV_B32_dpp undef $vgpr44(tied-def 0), $vgpr43, 322, 15, 15, 0, implicit $exec
12 errors generated when compiling for gfx1036.
Target //xla/extension:xla_extension failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 150.258s, Critical Path: 42.81s
INFO: 1972 processes: 451 internal, 1521 local.
FAILED: Build did NOT complete successfully
make: *** [Makefile:26: /build/0.6.0/cache/build/xla_extension-x86_64-linux-gnu-rocm.tar.gz] Error 1
** (Mix) Could not compile with "make" (exit status: 2).
You need to have gcc and make installed. If you are using
Ubuntu or any other Debian-based system, install the packages
"build-essential". Also install "erlang-dev" package if not
included in your Erlang/OTP version. If you're on Fedora, run
"dnf group install 'Development Tools'".

@jalberto I've just run build/build.sh rocm on a fresh AWS amd64 instance with Ubuntu 20.04 and it run without failure. I'm wondering if the issue could be that you build on the machine with the actual GPU and the build somehow runs additional logic/checks because of that, but I'm really just guessing.

@jonatanklosko that could be, but I am not mounting any device, so the container has not access to /dev/dri
I will continue trying around, maybe is my system, but the main reason to use containers to build is to isolate from the host, so it is very odd

@Eiji7 you can try the new release and use ROCm 6.0, see https://github.com/elixir-nx/xla/issues/82#issuecomment-2124230058.

@jonatanklosko Oh, that's definitely interesting, however I would need to wait for Gentoo maintainers first since version 6 is masked because of runtime issues, see:

# Patrick Lauer<EMAIL_ADDRESS>(2023-12-23)
# ROCm-6 builds but has runtime issues for me
Source: gentoo/gentoo@563b5ab

Yeah, it looks like latest XLA requires 6.0+, so I think this ship has sailed on this side.
I don't think there's anything else we can do for 5.7, so I'm going to close this in favour of #82. Feel free to drop more comments if anything changes!

For what it's worth, IREE might be able to provide a way out. We're focusing on Metal support, but we just might get ROCm "for free"


CXF-8698: Content-ID of attachments for outgoing requests are URL-decoded instead of URL-encoded

RFC-2392 (https://datatracker.ietf.org/doc/html/rfc2392) says:
  content-id = url-addr-spec
  url-addr-spec = addr-spec ; URL encoding of RFC 822 addr-spec

RFC-822 addr-spec (https://datatracker.ietf.org/doc/html/rfc822#appendix-D) says:
    addr-spec = local-part "@" domain ; global address

In the same vein, as RFC-2392 (https://datatracker.ietf.org/doc/html/rfc2392) says:
A "cid" URL is converted to the corresponding Content-ID message
header [MIME] by removing the "cid:" prefix, converting the % encoded
character to their equivalent US-ASCII characters, and enclosing the
remaining parts with an angle bracket pair, "<" and ">".

@deki @ffang @dkulp guys may I ask you please to take a look? Attempt to make Content-ID behavior more compliant to the specification (+ fixing some bug reports), thank you!

Thanks for looking into that @reta. I remember I was looking into a proposed fixed a few years back and missed the errata doc for the RFC: https://www.rfc-editor.org/errata/rfc2392
To me the change looks good but we don't have that many testcases covering all the use-cases.
I noticed there is another issue related to cid: https://issues.apache.org/jira/browse/CXF-8706
We should probably fix it within the same release.

To me the change looks good but we don't have that many testcases covering all the use-cases.

Thanks @deki , I added a few but still the coverage indeed could be improved

I noticed there is another issue related to cid: https://issues.apache.org/jira/browse/CXF-8706

Yes, I saw this one, I will take care of it once we this fix gets in, thank you.

Yes, this change is causing outgoing content-ids to be ENCODED. But unfortunately it also breaks the DECODE of incoming message. Content-ID headers do not contain "cid:-prefix as assumed here:
https://github.com/apache/cxf/pull/950/commits/221456aa5a515589b3bcda07a879de1b6e5e458c#diff-e3efb80d0a98bbbd7f6eddd3c021c5fb5ab05ea2ee8d97dc68026f6345e5a509R227
So after picking this change, I can see that outgoing headers are encoded but incoming messages are not decoded anymore. So I think there has to be a different condition to decide between en/decoding.

Thanks @mash-sap , may I ask you please for to confirm, I am trying to understand the case: with this change non-cid: prefixed Content-ID header is encoded on serializer side and is not decoded on deserializer side (when header extraction happens), correct?

Eaxctly @reta.
Outgoing Content-ID is encoded, but incoming message Content-ID is not decoded.

@mash-sap thanks for heads up, I will take a look shortly, we may fix that by properly decoding  in the deserializer.


can't pull scratch

I.E., the scratch image.

Should be able to say 'docker pull scratch', or select scratch from the list of images.

Not a kitematic issue, but a docker issue - Please close and re-open in docker :)

Thank you for looking into this, kind sir.
On Wed, Jul 22, 2015 at 11:21 PM, FrenchBen<EMAIL_ADDRESS>wrote:

Not a kitematic issue, but a docker issue - Please close and re-open in
docker :)
—
Reply to this email directly or view it on GitHub
https://github.com/kitematic/kitematic/issues/854#issuecomment-123959064
.


Loading multiple pages with jQuery (or possibly any heavier JS) concurrently doesn't work

<EMAIL_ADDRESS>commented:

Ubuntu 11.04, PhantomJS 1.3. Let's say we have a server that returns this HTML:
<!DOCTYPE html>
<html>
<head>
<title>test</title>
<meta charset="utf-8">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.js"></script>
</head>
<body>
hello
</body>
</html>
Now, we run the following PhantomJS script:
var page1 = require('webpage').create();
var page2 = require('webpage').create();
var url = encodeURI('http://localhost:4567');
function getContent() {
return document.querySelector('body').textContent;
};
page1.open(url, function() {
console.log(page1.evaluate(getContent));
});
page2.open(url, function() {
console.log(page2.evaluate(getContent));
});
The result should be:
hello
hello

But is:
null
hello
If you remove the <script> tag, it works.

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #298.
:star2:   4 people had starred this issue at the time of migration.

+1

@arsonik This bug is very old.  What version are you seeing it with?


Improve the stateSchema for EventIO

From https://github.com/phetsims/phet-io/issues/1774, some nested types were specified as EventIO, but that didn't seem to match up with what was happening at runtime.  Here are my notes:
    relatedTarget: NullableIO( ObjectLiteralIO ),  // TODO https://github.com/phetsims/phet-io/issues/1774 We thought this was supposed to be EventIO, but it was coming up as {data-trail-id: "380-381-466-473-468-693-760-759-734"}
 // ...
    target: NullableIO( ObjectLiteralIO ), // TODO https://github.com/phetsims/phet-io/issues/1774 We thought this was supposed to be EventIO, but it was coming up as an empty object

I'm a bit confused about EventIO... it seems to be mixing and matching a lot of different types of DOM events. Presumably everything being NullableIO means it only records that's there?
We should be referring to https://developer.mozilla.org/en-US/docs/Web/API/Event, target/relatedTarget definitely wouldn't be EventIOs... look like they're anything implementing this interface: https://developer.mozilla.org/en-US/docs/Web/API/EventTarget

Arg, sorry for the confusion. Yes of course those wouldn't be EventIO.
I think we should leave as is. Currently there doesn't seem to be need for anything more specific, and we aren't consistently using anything from the EventTarget interface.
I'm going to remove the TODOs and close this issue. Please reopen if you disagree.


Provide info on job params in YAML

Need API to retrieve job parameters from YAML config (in some sense they are perceived as "default" by users).

In fact, for SingleJob the best way would be to replace
public JobMetadata getMetadata() {
    return delegate.getMetadata();
}

with
public JobMetadata getMetadata() {
    return merge(execution.getParams(), delegate.getMetadata());
}

This seems to muddle the distinction between job singleton parameters and parameters of a given job run. Whether this is important or not, I have no idea yet.

After discussing offline, it actually makes sense, as "execution" is simply a param set.

While this issue is still something that we will need to address, it begs a bigger question on the distinction between a job and an execution, and will probably result in refactoring Job API (e.g. base metadata can be gathered from annotations, while execution metadata may be passed to the "run" method). So closing this task, as we won't be implementing it as described.


STILL: Current song error: no song.

I downloaded the most recent release, downloaded the most recent uncompiled version (which was said to fix the issue) and replaced the files in /resources/app (Windows) with those of the uncompiled version. The issue persists. The new UI looks nicer at least. Keep up the good work and let's see when I can go back to using this awesome app!

We will fix this on next release

@theluckyg for impatient ppl :D : https://github.com/emilioastarita/lyricfier/issues/71

Hi, When it will be fixed?

Still happening, --product-version=Spotify/<IP_ADDRESS>

Still happening
Spotify Version = <IP_ADDRESS>7.g256699aa

Still happening.
Win 8.1 64bit
Spotify <IP_ADDRESS>8.gde3fc4b2

Win 10 64bit
Spotify <IP_ADDRESS>5.ge6ca9946

The same for me
Max OSX 10.12.6
Spotify <IP_ADDRESS>2.gbb40dab8

Also here
Win 10 64-Bit
Spotify <IP_ADDRESS>9.g4637b02a

Could you please try last release?
https://github.com/emilioastarita/lyricfier/releases/tag/0.2.6
thx!

I'm closing this as should be solved in last release.

But yet still happening in linux... any recent fix?

@rgalhama Maybe this is the problem: https://github.com/emilioastarita/lyricfier/issues/103#issuecomment-407372908

Looks like it @luisramirez-m , I'll move it to this thread. Thanks!


How can I straighten the segmentation boundary?

I am doing image segmentation with mask rcnn.
But image segmentation boundary is vaguely expressed.
I want straighten boundary.
What should I do?
Simply Increase data learning?

@haspberry If you are only image segmentation, you can try mmseg, if it is instance segmentation and the boundary is emphasized, you can consider increasing the roialign output size or the pointrend algorithm.


"You rock!" screen comes up when you lose

I'm trying to refine my Humans Gold Rush code against my own Ogres code (since it's currently ranked #6), and at the end of the simulation (when Ogres win), the "You Win!" screen popped up. At first, I thought this was because, as I wrote the Ogres code, "I" did actually win.
However, I also see it when watching replays of games against other users where I lost, so I'm not sure what's happening.

I'm going to go ahead and close this, since it's only an issue for old-style ladder levels, and I don't want to mess around in the script state restoration bug stuff for those.


Error when trying to run the editor

Hi,
When I try to run the editor I receive an AttributeError saying that 'module' object has no attribute  'Progress'
Have you ever had this issue? Do you have any suggestions?
I tried to manually import html_helper in command line, it gave me the same error.
P.S.: I am new to python, so I apologize if I am asking a stupid question.
Regards,
Koray

Hello @bashkan ,
The problem is caused by the fact that you installed remi from pypi, and you downloaded the editor from the master branch. The remi version on master branch is updated with new features, in this case the new feature is the Progress widget.
You can fix the problem in two ways:

download the older editor branch from here https://github.com/dddomodossola/remi/tree/v1.2.2 ;
install the most updated remi version directly from GitHub master "branch pip install git+https://github.com/dddomodossola/remi.git"

Have a good development

On pypi you find the stable version, without the latest updates.
Here, on GitHub master branch you have an "unstable" but most updated version.
In order to install the most updated version (the one on github) run the following command:
pip install git+https://github.com/dddomodossola/remi.git

Hello,
Since "pip install git+https://github.com/dddomodossola/remi.git" required that I have git installed, I preferred to download the older editor and it worked perfectly.
You have been great help, thank you for your support and the wonderful software.
Best Regards,
Koray


Implement hyperclick package

Part of Nuclide is the hyperclick package, https://atom.io/packages/hyperclick, it allows for interacting with text in the editor while holding the alt key, via a service.
Some thoughts of things we could implement with this.

Jump to definition.
allow quick fixes to define syntax errors they are associated with

for example quick fix to implement an interface could be attached to the, the syntax error for a interface not being implemented.

+1 this would be awesome!

Is anyone working on this?

Nope :rose:

+1

+1

This is very nice, but there is a problem using the ctrl-key, since this key is used to make multiple selections/use multiple text cursors in Atom (which is very useful). Maybe it is better to use the alt-key as described in the readme of hyperclick:

<alt> or <alt-mousemove> underlines clickable text under the mouse.
<alt-mousedown> performs the action associated with the clickable text.
<cmd-alt-enter> performs the action on the text under the cursor.

@markogresak Atom Typescript implement hyperclick provider for jump to declaration since version 10.0.1 . You can use alt key that hyperclick mapped.

It seems the ctrl-key is mapped on Windows instead of the alt-key. Submitted a PR to change this behavior: https://github.com/facebook/nuclide/pull/612

I agree with @markvandenbrink about the keymap issue. I'm used to using cmd + click to make multiple selections.
Is this also only supposed to work with typescript files? Seem to see the white hyperclick underline in every file type I'm in when holding down cmd which makes this feature buggy.

If i'm not mistaken, the integration is gone again with atom typescript v11? 😅

@robofish, it sure is. Command+click is also used to place multiple cursors and if hyperclick is only used for jumping to the definition, I didn't see the point in keeping it since clicking on the symbol and pressing F12 is very close, though I agree that switching from the mouse to the keyboard is not perfect. I might be convinced that it make sense to use with quickfixes though.

Hyperclick added an option to change which modifier(s) is used, so that it doesn't have to interfere with multiple cursors. I'd also ask that the integration be added back.

I implemented this and made a pull request, which you can test if you want: https://github.com/TypeStrong/atom-typescript/pull/1265


Integrated terminal doesn't work after activating conda environment

After activating my virtual env by using "conda activate
Environment data

VS Code version: 1.36.1
Extension version (available under the Extensions sidebar): 2019.6.24221
OS and version: Mac OS 10.14.5
Python version (& distribution if applicable, e.g. Anaconda): Anaconda
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Relevant/affected Python packages and their versions: XXX
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): Language, python.jediEnabled is unchecked

Expected behaviour
After activate my virtual env, python and pip should be the target version. and I can install packages in my virtual env other than the default.
Actual behaviour
which python shows:
/usr/local/bin/python, and I install packages then they are not located in my virtual env.
Steps to reproduce:

Conda: activate my created virtual environment by using "conda activate django-env"
2."conda env list" shows the env:
conda environments:
base /usr/local/anaconda3
django-env * /usr/local/anaconda3/envs/django-env
hawthron /usr/local/anaconda3/envs/hawthron
3."which python"
/usr/local/bin/python

But in Mac's default terminal or third-party terminal like iterm2. I do the same thing and the "which python" shows:
/usr/local/anaconda3/envs/django-env/bin/python.
So i can use pip to install packages in right place. not in default.

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
XXX

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
XXX

Thanks for reporting this issue, however I'm closing this as it is a known VS Code (upstream) issue, please check the following documentation for a temporary solution https://code.visualstudio.com/updates/v1_36#_launch-terminals-with-clean-environments (change the setting terminal.integrated.inheritEnv).

@DonJayamanne Yes, I changed the setting terminal.integrated.inheritEnv to false and can finally fix my problem.


MINOR: Pass compressionType config to producer in TestUtils.produceMessages

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ijuma trivial change to pass correctly compressionType config in TestUtils.produceMessages method.  Currently none of the tests are passing compressionType parameter. we can also cleanup by removing unused compressionType parameter.

Thanks for the PR. Hmm, this is a bit odd, has this changed recently?

I think this was there since old client changes.  Previously TestUtils.sendMessages  method with compressionType was used in old consumer related tests.  This was removed as part of old producer changes, migrated to produceMessages method.

@ijuma  Removed the unused parameter. Updated the PR.


cmd/gofmt

What version of Go are you using (go version)?
go version go1.7rc3 linux/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/usr/local/google/home/tmatsuo/go"
GORACE=""
GOROOT="/usr/lib/google-golang"
GOTOOLDIR="/usr/lib/google-golang/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build401308622=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
What did you do?
My gofmt formats spaces around operator differently.
package main

import (
        "fmt"
        "time"
)

func main() {
        time.Sleep(8 * time.Second)
        err := fmt.Errorf("test", time.Sleep(8*time.Second))
}

What did you expect to see?
I expect consistent rules about spaces around operators like:
package main

import (
        "fmt"
        "time"
)

func main() {
        time.Sleep(8 * time.Second)
        err := fmt.Errorf("test", time.Sleep(8 * time.Second))
}

Formatting of expressions depends on nesting. A multiplication stand-alone is formatted "a * b", but together with other lower-precedence operators is formatted as "a*b + c"; etc.
Working as intended.

PS: To be fair, one might argue that in this case, since we have a single argument, it is incorrect. See also: https://play.golang.org/p/LYF_I6JW0J . But we've been living with this for years now; changing it would cause unnecessary formatting changes in a lot of code and lead to unnecessary churn. Let's leave this for the future (perhaps as part of a larger gofmt format update). Unfortunate.

Yeah I can live with that. Thanks for the explanation.


Fix warning for duplicate key under Ruby 2.2.0.

Warning was:
warning: duplicated key at line 29 ignored: :concealed

This PR is a dupe of #20.


Discord+ Wont Load

I keep attempting to use Discord+, a theme on BetterDiscord to allow customization to things such as the background, home icon, UI font, and so on.
When loading up Discord on Windows, BetterDiscord does not load Discord+. It is enabled, there is accurate information in Discord+, and I have already tried uninstalling and reinstalling Discord+. I just updated Better Discord to its newest version. I am currently using Windows 10, not Windows 11.
Below should be a screenshot of Discord+ being activated, but not running.

This repository and issues is not for themes or theme issues. If you have an issue Join the Discord  and make a support post.


Support "latest" Terraform version

Fetches the Terraform releases from Hashicorp and picks the latest released version.
This was requested in #669 and we need this feature as well.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: jvassbo sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Really would love this to be merged.  Any updates?

any update on this? would like to see it aswell.

Not letting this hang into 2021. No feedback for 10+ months, so much for trying to contribute. /s


Broken step results in a successful run

Describe the bug
(Probably related to https://github.com/ozontech/allure-go/issues/4)
A single test with a broken step results in a passed test.
The test
func Test_AllureExample(t *testing.T) {
	runner.Run(t, "Allure demo", func(t provider.T) {
		t.WithNewStep("First step", func(sCtx provider.StepCtx) {
			sCtx.Logf("Demo break")
			sCtx.Broken()
		})
	})
}

The report (exluding labels):
{
    "name": "Allure demo",
    "fullName": "Test_AllureExample/Allure_demo",
    "status": "passed",
    "statusDetails": {
        "message": "",
        "trace": ""
    },
    "start":<PHONE_NUMBER>758,
    "stop":<PHONE_NUMBER>758,
    "uuid": "f34c46a8-6bd0-11ed-bd95-a45e60d5053f",
    "historyId": "baa17e747dc3baf09c0ad0b7a00c6251",
    "testCaseId": "3948cbd85816212b9f92d81b0b03b207",
    "labels": [
    ],
    "steps": [
        {
            "name": "First step",
            "status": "broken",
            "start":<PHONE_NUMBER>758,
            "stop":<PHONE_NUMBER>758
        }
    ]
}

Note that step has a proper broken status, but the test has a passed status.
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Create a single test.
Define one step in the test.
use broken() in this step's function.
Check report.

Expected behavior
The test is marked as Broken in the report.
Additional context
I have some questions regarding this issue:

Is it a bug or is it intended? If intended, how can i apple Broken status to a test?
What should be done either way with provider.T of my test after setting some step to broken()? There is no BreakNow() fn, so i just have to end the test execution naturally after a broken step?
Which go test status (skipped / failed) will be applied to the test, if it s properly set as Broken by the library?

Hello, @Emptyfruit !
Thank you for your issue.
Q: Is it a bug or is it intended? If intended, how can i apple Broken status to a test?
A: For now its intended - broken status for test is panic only. All other cases should be handled with assert/require failing. The reason of this is broken status semantics. Broken means break of test code, not test logic. So you can broke your step, but you should not break with it your test.
Can you please describe case that you tries to solve with Broken() method?
Q: What should be done either way with provider.T of my test after setting some step to broken()? There is no BreakNow() fn, so i just have to end the test execution naturally after a broken step?
A: Expected behavior is use t.FailNow() for shutting down in unexpected situations
Q: Which go test status (skipped / failed) will be applied to the test, if it s properly set as Broken by the library?
A: we use failed cause skipped has different behaviour and semantics (this is the reason why you can't just call Broken() to set broken status.

Thanks for the quick and detailed replies.
Our use-case is pretty complex: we have a set of tests cases (from go project perspective it is dynamic subtests). All cases are based on a custom data format and stored remotely, so getting an actual "test case" is a process of several steps (finding, parsing, etc.) and each can fail for different reasons. So if the "preparation" of a test case fail, we consider it broken. And only if it is prepared and we have and actual case to test, it can actually fail or succeed. It seems like a legit use of broken to me.
I believe that if Allure has this status for a test itslef (no only steps) and even statistics for it, there should be an option to use it.
Btw, i tried dailymotion/allure-go and it has Break and BreakNow() and it works as i'd imagine. (though, the lib itself has a very limited reporting functionality).
Also i'd note that currently this aspect feels a bit "undecided" when using you library. By default if i just break a step the test will be considered successful, which a bit counter-intuitive for me. imho, i could not call a testw ith a broken step "successful". But i'm new to qa engeneering, tbh.

@Emptyfruit , if you have some tests that are depends from each other best solution in this case is to use asserts
Go allows you something like this:
func (s *MySuite) TestMyTest(t provider.T)  {
     var (
           err error

           firstSubtestResult SomeInterface
           secondSubtestResult SomeInterface
           thirdSubtestResult SomeInterface
     )

     t.Run("First subtest", func(t provider.T) {
          firstSubtestResult, err = s.SomeCli.SomeApiCall(...)
          t.Require().NoError(err)
     }
     t.Require().NotNil(firstSubtestResult)

     t.Run("Second subtest", func(t provider.T) {
          secondSubtestResult, err = s.SomeCli.SomeApiCall(...)
          t.Require().NoError(err)
     }
     t.Require().NotNil(secondSubtestResult)

     t.Run("Third subtest", func(t provider.T) {
          thirdSubtestResult, err = s.SomeCli.SomeApiCall(...)
          t.Require().NoError(err)
     }
     t.Require().NotNil(thirdSubtestResult)
}

In your case it can be best solution. Each part of your big e2e test should be asserted. Cause failing of subtest is defect, not issue with tests.
I agree that Broken() behavior in StepCtx interface is unclean, but the reason, why it works in that way is simple - if you need panic inside step, but don't wan't to fail test (panic expected) it will be Broken() called inside the library to set status to the step, but test still will be green.
Also "testing" library of golang not provides broken status to the tests (only success/fail) so broken can be confusing in many cases. Native way to end test immidiately on reaching some condition is FailNow() for Go

It also ok to use closures in your tests. It kind of native way to exchange data between lambda calls inside the go

Native way to end test immidiately on reaching some condition is FailNow() for Go

BTW, the reason of this is specific goway to work with exceptions (returning errors as function result and panic handling). You don't need to throw exceptions like in Java or C# - cause panic is really unexpected behavour (like NPE, or Stackoverlow). So all other situations that provide errors is actually expected.
So if you have errors in go - it means that test failed
If you have unhandled panics - it means that test broken
Please, leave feedback if you have any other questions. I will be enjoyed to help you in building tests with allure-go :)

Thank your for interesting advices. I'll try to clarify our situation a bit. I cannot have suits the way you implement them in go, because all my cases are dynamic. So i have only one TestAllCases(t *testing.T) test in my go project. So each dynamic case will be a separate suite in my report (which is totally fine by me).
I'd prefer not to treat the "setup" steps as part of the test. It is just a matter of convenience. If i open a report and see 100 failed tests, i have no way of knowing which failure is an indeed a failed test of functionality and which failure is just a misconfigured test case (which lives inside another project and is managed by another team). So i'd like to separate valid cases that failed (have to fix product) and invalid cases that say nothing about the product's functionality (have to fix test case or test case repo).
As i understand, i could define one Suite and treat each dynamic test case as a subtest of this suite. That way i'd even get my "broken" functionality, since setup-steps will become substeps and breaking will propogate to the level of my case.
So in my report i will have 1 suite with hundrends of steps (cases) inside. But i think that having all tests as a steps of one suite is kind of a workaround and i'll loose most allure functionality in the end, such as history, tags, stats, timing, etc.
I understand your position on panics and error handling. But still, i think that providing an api to set test's status to Broken (even if i have to explicitly set it) will just add flexibility. In the end, it is just a matter of interpretation of a report. As i undersant now, there is no way whatsoever to get a testw ith status Broken in your report. So i see reasons not to use it for some implicit behaviour, but no reasons to restrict setting it manually.
So in the end, i'd be happy just to have a Break() or BreakNow() method, which would do the same as Fail() and Failnow() but set the suite's status to Broken, which i would use explicitly. I don't see much harm in it, but see some flexibility.


Unable to resolve module ~/example from /home/example.js Module does not exist in the module map

The plugin is working great on my React Native app, but i'm getting this error message when i'm try to "Publish" the application using Expo XDE.
How to resolve?
Unable to resolve module "~/telas/Home/Tile" from "/home/tonin/Documentos/react/pontuamais/App.js": Module does not exist in the module map

Solved!
I had forgotten to add babel-plugin-root-import to my .babelrc on production env.
"production": {
"plugins": ["transform-react-jsx-source", "babel-plugin-root-import"]
}


Fix margins on QR code

Was causing scrollbar. Unneeded.

@keybase/react-hackers

The commits 5753ede39e6e...81327f053a4a introduce visual changes on linux. :mag_right: 2 changed

Changed: Code_Page-Show_Code_Mobile (before) (after)

Changed: Code_Page-Show_Code (before) (after)

Visdiff changes are the horizontal scrollbar going away.

The commits cdf37d5b0932...147ab4fd3602 introduce visual changes on linux. :mag_right: 2 changed

Changed: Code_Page-Show_Code_Mobile (before) (after)

Changed: Code_Page-Show_Code (before) (after)


ReferenceError: Blob is not defined

Describe the bug
I am trying to create a flow with the Conversational Retriever QA chain. I tried multiple document loaders but each one of them gave me a ReferenceError: Blob is not defined.
To Reproduce
Steps to reproduce the behavior:
you can try to create any flow with any document loader.
Expected behavior
for me to be able to chat with the LLM using the loaded documents.
Screenshots
here is the flow I am using.

Setup

OS: Linux
Browser: Chrome.

Additional context
These are the console logs:
    at Csv_DocumentLoaders.init (/home/mohdhd/.npm/_npx/8b95a19c5c9c8708/node_modules/flowise-components/dist/nodes/documentloaders/Csv/Csv.js:43:22)
    at buildLangchain (/home/mohdhd/.npm/_npx/8b95a19c5c9c8708/node_modules/flowise/dist/utils/index.js:203:72)
    at async /home/mohamed/.npm/_npx/8b95a19c5c9c8708/node_modules/flowise/dist/index.js:235:44

I managed to fix it by updating my node version to 18.15.0

Hi mondhd i got the same error i tried even upgrading to 18.15 but still facing same issue.

Hi @CharnSrinivas,
Troubleshoots steps:

If you're using linux or windows NVM, make sure it's running the correct version of NodeJS.
Re-install Flowise; Export your flows before you re-install.


Sparql Examples

Hi an eta on sparql examples ?

@mickdelaney They should be out early next year.

Hi an eta on sparql examples ?

Hi, an eta on sparql examples?

Hi, please add examples for SPARQL....I feel like we can't use it with SPARQL as all the examples are in Gremlin

Hi All, Yes, we have SPARQL examples in process, and you absolutely can use Neptune with SPARQL. You should see the first examples come out this month.

Hi, an eta on sparql examples?