Sam Chen

shouldn't put the flags in the bazelrc, but in each libraries and binaries separately.

Can you descript this issue in more details?

> The CI tests failed. > It seems like the failed tests is related to the cross compilation since it has the `bazel` option `--crosstool_top` and `--host_crosstool_top`? the test failed...

~these two commands should have the same output. This PR has no compilation errors in my environment. it's related to the container will update later.~ @marktwtn I was not fully...

> Here comes with 2 questions: > > 1. Should I add another test for larger input data size or just modify the input data size of the original test?...

you can test the `test_transaction` directly and since it gets `Segmentation fault` you can enable address sanitizer like: `bazel test -c dbg --config asan --config bootlin_x86_64_core_i7 //common/model/tests:test_transaction`. You can just...

These two cases are failed on system toolchain as well when I run `bazel test -c dbg --copt=-msse4.2 //common/...` * //common/model/tests:test_transaction * //common/model/tests:test_tryte_transaction

@marktwtn Could you write benchmarks for `trits_to_trytes`, `trytes_to_trits` and put it in `//common/trinary/benchmark`? thanks.

> > @marktwtn Could you write benchmarks for `trits_to_trytes`, `trytes_to_trits` and put it in `//common/trinary/benchmark`? thanks. > > It seems that there are no other benchmark in the other directories...

Hey, @marktwtn how are you? do you need any help on Bazel or else?