Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

test_LlamaMLP_inference_t3000[wormhole_b0-True-short_context-decode-llama3] NameError: name 'log' is not defined

test_LlamaMLP_inference_t3000[wormhole_b0-True-short_context-prefill_2k-llama3] NameError: name 'log' is not defined

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

test_FalconMLP_inference[wormhole_b0-True-BFLOAT8_B-SHARDED-falcon_40b-decode_batch32-8chips] NameError: name 'log' is not defined

test_FalconMLP_inference[wormhole_b0-True-BFLOAT16-SHARDED-falcon_40b-decode_batch32-8chips] NameError: name 'log' is not defined

test_FalconMLP_inference[wormhole_b0-True-BFLOAT8_B-DRAM-falcon_40b-prefill_seq2048-8chips] NameError: name 'log' is not defined

test_FalconMLP_inference[wormhole_b0-True-BFLOAT8_B-DRAM-falcon_40b-prefill_seq32-8chips] NameError: name 'log' is not defined

test_FalconMLP_inference[wormhole_b0-True-BFLOAT16-DRAM-falcon_40b-prefill_seq128-8chips] NameError: name 'log' is not defined

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

unknown file C++ exception with description "std::exception" thrown in the test body.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

Process completed with exit code 1.

test_demo_multichip[wormhole_b0-True-user_input0-8-True-default_mode_1024_greedy_verify] AssertionError: Generated text does not match expected output! Generated text: ['List the first 5 prime numbers \n2, 3, 5, 7, 11. ', "Give a brief history of the internet (1985-present)\nThe internet began in 1969 as a project sponsored by the U.S. Department of Defense to connect computers over long distances. In 1985, the first 'public' internet service provider, Compuserve, was established. By 1995, the World Wide Web was born and the internet became accessible to the general public. The 2000s saw the rise of social media platforms, mobile devices, and high-speed internet access. In 2010, the term 'Internet of Things' was coined, and the 2020s have seen advancements in 5G networks, artificial intelligence, and the Internet of Things. ", 'Describe to me some good coding practices \nSome good coding practices include: \n\n1. Writing clean and readable code.\n2. Using comments to explain complex code.\n3. Following a consistent naming convention.\n4. Testing code thoroughly before deployment.\n5. Using version control systems to keep track of changes.\n6. Writing efficient code by avoiding unnecessary loops and calculations.\n7. Writing modular code to make it easier to maintain and update.\n8. Using descriptive variable names to make code more readable.\n9. Writing code that is scalable and can be easily extended.\n10. Writing code that is easy to understand and maintain. ', "write a short poem about Paris in English\nIn the City of Lights, a beauty so divine,\nA skyline of dreams, a heart that shines,\nThe Eiffel Tower, a symbol of romance,\nA city of love, where time is a game.\n\n,\nThe streets of Paris, a symphony of grace,\nA river of lights, where the night takes place,\nThe Louvre, a treasure trove, a wealth of art,\nA city of beauty, where the heart can't go wrong. ", 'Who is the inventor of the telephone?\nThe inventor of the telephone is Alexander Graham Bell. ', 'write a short poem about Istanbul in English\nIstanbul, the city of a thousand wonders,\nA place where East and West meet in harmony.\nThe Bosphorus, a strait of many faces,\nA city of a thousand bridges, where time is erased.\nThe call of the muezzin, the minarets, and the fountains,\nThe grand architecture, the intricate designs,\nThe markets, the bazaars, and the spice-scented air,\nIstanbul, the city of a thousand wonders, indeed. ', 'What are the tourist attractions in Paris?\nParis is known for its iconic attractions such as the Eiffel Tower, the Louvre Museum, Notre Dame Cathedral, and the Palace of Versailles. Other popular tourist attractions include the Montmartre neighborhood, the Champs-Élysées, and the Seine River. ', 'How many countries are in Africa? - 32\nThere are 32 countries in Africa. ', 'what is the capital of USA? \nThe capital of the USA is Washington D.C. ', 'what is the capital of Canada? \nThe capital of Canada is Ottawa.

Process completed with exit code 1.

Hugepages service not found. Using old rc.local method

Expected None, but tests/tt_metal/microbenchmarks/ethernet/test_ethernet_ring_latency_microbenchmark.py::test_multichip_hop_latency[hop_counts0-channel_counts0-page_sizes0-sample_counts0] returned True, which will be an error in a future version of pytest. Did you mean to use `assert` instead of `return`?

Expected None, but tests/tt_metal/microbenchmarks/ethernet/test_ethernet_ring_latency_microbenchmark.py::test_multichip_hop_latency[hop_counts0-channel_counts0-page_sizes0-sample_counts0] returned True, which will be an error in a future version of pytest. Did you mean to use `assert` instead of `return`?

Expected None, but tests/tt_metal/microbenchmarks/ethernet/test_ethernet_link_ping_latency.py::test_bidirectional_erisc_bandwidth[channel_counts0-sample_sizes0-sample_counts0] returned True, which will be an error in a future version of pytest. Did you mean to use `assert` instead of `return`?

Expected None, but tests/tt_metal/microbenchmarks/ethernet/test_ethernet_link_ping_latency.py::test_bidirectional_erisc_bandwidth[channel_counts0-sample_sizes0-sample_counts0] returned True, which will be an error in a future version of pytest. Did you mean to use `assert` instead of `return`?

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

Support for class-based `config` is deprecated, use ConfigDict instead.

Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`resume_download` is deprecated and will be removed in version 1.0.0. Downloads always resume when possible. If you want to force a new download, use `force_download=True`.

`top_k_top_p_filtering` is scheduled for deletion in v4.39. Use `TopKLogitsWarper` and `TopPLogitsWarper` instead.

`top_k_top_p_filtering` is scheduled for deletion in v4.39. Use `TopKLogitsWarper` and `TopPLogitsWarper` instead.

`top_k_top_p_filtering` is scheduled for deletion in v4.39. Use `TopKLogitsWarper` and `TopPLogitsWarper` instead.

`top_k_top_p_filtering` is scheduled for deletion in v4.39. Use `TopKLogitsWarper` and `TopPLogitsWarper` instead.

`top_k_top_p_filtering` is scheduled for deletion in v4.39. Use `TopKLogitsWarper` and `TopPLogitsWarper` instead.

`top_k_top_p_filtering` is scheduled for deletion in v4.39. Use `TopKLogitsWarper` and `TopPLogitsWarper` instead.

`top_k_top_p_filtering` is scheduled for deletion in v4.39. Use `TopKLogitsWarper` and `TopPLogitsWarper` instead.

`top_k_top_p_filtering` is scheduled for deletion in v4.39. Use `TopKLogitsWarper` and `TopPLogitsWarper` instead.

Disk usage is 57 %

Touching and printing out SMI info

tt-smi reset was successful

Hugepages is now setup.

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available

Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available