(T3K) T3000 frequent tests #1912
t3000-frequent-tests.yaml
on: workflow_dispatch
build-artifact
/
...
/
check-docker-images
6s
build-artifact
/
🛠️ Build Release ubuntu 20.04
2m 58s
Matrix: t3000-frequent-tests / t3000-frequent-tests
Annotations
3 errors, 37 warnings, and 22 notices
t3000-frequent-tests / t3k n300 mesh llama3.2-vision tests
Process completed with exit code 1.
|
t3000-frequent-tests / t3k tteager tests
Process completed with exit code 1.
|
t3000-frequent-tests / t3k mixtral tests
Process completed with exit code 1.
|
t3000-frequent-tests / t3k ethernet tests:
python_env/lib/python3.8/site-packages/_pytest/python.py#L199
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`?
|
t3000-frequent-tests / t3k ethernet tests:
python_env/lib/python3.8/site-packages/_pytest/python.py#L199
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`?
|
t3000-frequent-tests / t3k ethernet tests:
python_env/lib/python3.8/site-packages/_pytest/python.py#L199
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`?
|
t3000-frequent-tests / t3k ethernet tests:
python_env/lib/python3.8/site-packages/_pytest/python.py#L199
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`?
|
t3000-frequent-tests / t3k falcon40b tests:
python_env/lib/python3.8/site-packages/huggingface_hub/file_download.py#L1142
`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`.
|
t3000-frequent-tests / t3k falcon40b tests:
python_env/lib/python3.8/site-packages/huggingface_hub/file_download.py#L1142
`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`.
|
t3000-frequent-tests / t3k falcon40b tests:
python_env/lib/python3.8/site-packages/huggingface_hub/file_download.py#L1142
`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`.
|
t3000-frequent-tests / t3k falcon40b tests:
python_env/lib/python3.8/site-packages/huggingface_hub/file_download.py#L1142
`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`.
|
t3000-frequent-tests / t3k falcon40b tests:
python_env/lib/python3.8/site-packages/huggingface_hub/file_download.py#L1142
`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`.
|
t3000-frequent-tests / t3k falcon40b tests:
python_env/lib/python3.8/site-packages/huggingface_hub/file_download.py#L1142
`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`.
|
t3000-frequent-tests / t3k falcon40b tests:
python_env/lib/python3.8/site-packages/huggingface_hub/file_download.py#L1142
`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`.
|
t3000-frequent-tests / t3k falcon40b tests:
python_env/lib/python3.8/site-packages/huggingface_hub/file_download.py#L1142
`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`.
|
t3000-frequent-tests / t3k falcon40b tests:
python_env/lib/python3.8/site-packages/huggingface_hub/file_download.py#L1142
`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`.
|
t3000-frequent-tests / t3k falcon40b tests:
python_env/lib/python3.8/site-packages/huggingface_hub/file_download.py#L1142
`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`.
|
t3000-frequent-tests / t3k llama3.2-vision tests:
python_env/lib/python3.8/site-packages/pydantic/_internal/_config.py#L291
Support for class-based `config` is deprecated, use ConfigDict instead.
|
t3000-frequent-tests / t3k llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L120
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L137
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L162
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k llama3.2-vision tests:
python_env/lib/python3.8/site-packages/pydantic/_internal/_config.py#L291
Support for class-based `config` is deprecated, use ConfigDict instead.
|
t3000-frequent-tests / t3k llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L120
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L137
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L162
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k llama3.2-vision tests:
python_env/lib/python3.8/site-packages/pydantic/_internal/_config.py#L291
Support for class-based `config` is deprecated, use ConfigDict instead.
|
t3000-frequent-tests / t3k llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L120
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k n300 mesh llama3.2-vision tests:
python_env/lib/python3.8/site-packages/pydantic/_internal/_config.py#L291
Support for class-based `config` is deprecated, use ConfigDict instead.
|
t3000-frequent-tests / t3k n300 mesh llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L120
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k n300 mesh llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L137
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k n300 mesh llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L162
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k n300 mesh llama3.2-vision tests:
python_env/lib/python3.8/site-packages/pydantic/_internal/_config.py#L291
Support for class-based `config` is deprecated, use ConfigDict instead.
|
t3000-frequent-tests / t3k n300 mesh llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L120
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k n300 mesh llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L137
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k n300 mesh llama3.2-vision tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L162
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k llama3 tests:
python_env/lib/python3.8/site-packages/pydantic/_internal/_config.py#L291
Support for class-based `config` is deprecated, use ConfigDict instead.
|
t3000-frequent-tests / t3k llama3 tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L120
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k llama3 tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L137
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k llama3 tests:
python_env/lib/python3.8/site-packages/llama_models/llama3/api/datatypes.py#L162
Pydantic V1 style `@validator` validators are deprecated. You should migrate to Pydantic V2 style `@field_validator` validators, see the migration guide for more details
|
t3000-frequent-tests / t3k llama3 tests:
models/demos/llama3/tests/test_llama_chunked_generation.py#L26
record_property is incompatible with junit_family 'xunit2' (use 'legacy' or 'xunit1')
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
weka-mount-hugepages-service-found
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
hugepages-service-found-startup
Hugepages service found. Command returned with exit code 3. Restarting it so we can ensure hugepages are available
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
TTMetal_build_any
|
186 MB |
|
packages-ubuntu-20.04-amd64-Release-x86_64-linux-clang-17-libcpp
|
89.4 MB |
|