Skip to content

PR #3851 #1374

Sign in to view logs

PR #3851

PR #3851 #1374

GitHub Actions / JEST Tests succeeded Feb 2, 2025 in 0s

187 passed, 7 failed and 4 skipped

Tests failed

❌ packages/grid_client/tests/test-reports/report.xml

198 tests were completed in 2838s with 187 passed, 7 failed and 4 skipped.

Test suite Passed Failed Skipped Time
algorand.test.ts 5✅ 2⚪ 5s
algorand.test.ts 1✅ 69s
capacity_planner.test.ts 8✅ 15s
casperlabs.test.ts 1✅ 96s
compute_capacity.test.ts 6✅ 702ms
contracts.test.ts 5✅ 49s
currency.test.ts 18✅ 6s
discourse.test.ts 1⚪ 825ms
funkwhale.test.ts 1✅ 221s
gateways.test.ts 1❌ 270s
kubernetes.test.ts 3❌ 346s
kvstore.test.ts 1✅ 13s
mattermost.test.ts 1✅ 97s
network_light.test.ts 7✅ 818ms
nextcloud.test.ts 1✅ 114s
nodepilot.test.ts 1⚪ 829ms
peertube.test.ts 1✅ 101s
presearch.test.ts 1✅ 90s
qsfs.test.ts 2❌ 414s
query_to_string.test.ts 6✅ 365ms
root_fs.test.ts 2✅ 220ms
stellar.test.ts 7✅ 40s
subsquid.test.ts 1✅ 108s
taiga.test.ts 1✅ 151s
tfchain.test.ts 8✅ 174s
umbrel.test.ts 1✅ 89s
vm.test.ts 3✅ 1❌ 222s
volume.test.ts 3✅ 969ms
wordpress.test.ts 1✅ 96s
workload.test.ts 65✅ 1s
zdb.test.ts 1✅ 41s
zmachine_light.test.ts 11✅ 794ms
zmachine.test.ts 12✅ 767ms
zmount.test.ts 8✅ 681ms

✅ algorand.test.ts

 TC1247 - Algorand: Create Account
  ✅ TC1247 - Algorand: Create Account
 TC1248 - Algorand: Import Account
  ✅ TC1248 - Algorand: Import Account
 TC1249 - Algorand: Get Account
  ✅ TC1249 - Algorand: Get Account
 TC1250 - Algorand: Check if Account exists
  ✅ TC1250 - Algorand: Check if Account exists
 TC1251 - Algorand: List Accounts
  ✅ TC1251 - Algorand: List Accounts
 TC1252 - Algorand: Get Account assets
  ⚪ TC1252 - Algorand: Get Account assets
 TC1253 - Algorand: Get Account assets by address
  ⚪ TC1253 - Algorand: Get Account assets by address

✅ algorand.test.ts

 TC2727 - Applications: Deploy Algorand
  ✅ TC2727 - Applications: Deploy Algorand

✅ capacity_planner.test.ts

 TC1239 - Capacity Planner: Get Farms
  ✅ TC1239 - Capacity Planner: Get Farms
 TC1240 - Capacity Planner: Get All Farms
  ✅ TC1240 - Capacity Planner: Get All Farms
 TC1241 - Capacity Planner: Get Nodes
  ✅ TC1241 - Capacity Planner: Get Nodes
 TC1242 - Capacity Planner: Get All Nodes
  ✅ TC1242 - Capacity Planner: Get All Nodes
 TC1243 - Capacity Planner: Filter Nodes
  ✅ TC1243 - Capacity Planner: Filter Nodes
 TC1244 - Capacity Planner: Get Free Public IPs
  ✅ TC1244 - Capacity Planner: Get Free Public IPs
 TC1245 - Capacity Planner: Get Free Resources of a Specific Node
  ✅ TC1245 - Capacity Planner: Get Free Resources of a Specific Node
 TC1246 - Capacity Planner: Get Farm ID From Farm Name
  ✅ TC1246 - Capacity Planner: Get Farm ID From Farm Name

✅ casperlabs.test.ts

 TC2683 - Applications: Deploy Casperlabs
  ✅ TC2683 - Applications: Deploy Casperlabs

✅ compute_capacity.test.ts

Compute Capacity module Compute Capacity instance is of type ComputeCapacity.
  ✅ Compute Capacity module Compute Capacity instance is of type ComputeCapacity.
Compute Capacity module Min values for cpu & memory.
  ✅ Compute Capacity module Min values for cpu & memory.
Compute Capacity module Max values for cpu & memory.
  ✅ Compute Capacity module Max values for cpu & memory.
Compute Capacity module cpu & memory doesn't accept decimal values.
  ✅ Compute Capacity module cpu & memory doesn't accept decimal values.
Compute Capacity module cpu & memory empty values.
  ✅ Compute Capacity module cpu & memory empty values.
Compute Capacity module An error should be thrown if cpu & memory negative values.
  ✅ Compute Capacity module An error should be thrown if cpu & memory negative values.

✅ contracts.test.ts

 TC1269 - Contracts: Create Node Contract
  ✅ TC1269 - Contracts: Create Node Contract
 TC1270 - Contracts: Create Name Contract
  ✅ TC1270 - Contracts: Create Name Contract
 TC1271 - Contracts: Get Node Contract By Node ID & Contract Hash
  ✅ TC1271 - Contracts: Get Node Contract By Node ID & Contract Hash
 TC1272 - Contracts: Get Name Contract
  ✅ TC1272 - Contracts: Get Name Contract
 TC1273 - Contracts: Update Node Contract
  ✅ TC1273 - Contracts: Update Node Contract

✅ currency.test.ts

Testing TFT module tft module to be instance of TFTUSDConversionService
  ✅ Testing TFT module tft module to be instance of TFTUSDConversionService
Testing TFT module should return value with 2 decimals.
  ✅ Testing TFT module should return value with 2 decimals.
Testing TFT module should convert to the correct value based on tftPrice.
  ✅ Testing TFT module should convert to the correct value based on tftPrice.
Testing TFT module convertTFTtoUSD function to throw if passed a negative value.
  ✅ Testing TFT module convertTFTtoUSD function to throw if passed a negative value.
Testing TFT module convertUSDtoTFT function returns a valid value.
  ✅ Testing TFT module convertUSDtoTFT function returns a valid value.
Testing TFT module convertUSDtoTFT function to throw if passed a negative value.
  ✅ Testing TFT module convertUSDtoTFT function to throw if passed a negative value.
Testing TFT module dailyTFT function returns a valid value.
  ✅ Testing TFT module dailyTFT function returns a valid value.
Testing TFT module dailyTFT function throws if passed anything other than a positive value.
  ✅ Testing TFT module dailyTFT function throws if passed anything other than a positive value.
Testing TFT module monthlyTFT function returns a valid value.
  ✅ Testing TFT module monthlyTFT function returns a valid value.
Testing TFT module monthlyTFT function throws if passed anything other than a positive value.
  ✅ Testing TFT module monthlyTFT function throws if passed anything other than a positive value.
Testing TFT module yearlyTFT function returns a valid value.
  ✅ Testing TFT module yearlyTFT function returns a valid value.
Testing TFT module yearlyTFT function throws if passed anything other than a positive value.
  ✅ Testing TFT module yearlyTFT function throws if passed anything other than a positive value.
Testing TFT module dailyUSD function returns a valid value.
  ✅ Testing TFT module dailyUSD function returns a valid value.
Testing TFT module dailyUSD function throws if passed anything other than a positive value.
  ✅ Testing TFT module dailyUSD function throws if passed anything other than a positive value.
Testing TFT module monthlyUSD function returns a valid value.
  ✅ Testing TFT module monthlyUSD function returns a valid value.
Testing TFT module monthlyUSD function throws if passed anything other than a positive value.
  ✅ Testing TFT module monthlyUSD function throws if passed anything other than a positive value.
Testing TFT module yearlyUSD function returns a valid value.
  ✅ Testing TFT module yearlyUSD function returns a valid value.
Testing TFT module yearlyUSD function throws if passed anything other than a positive value.
  ✅ Testing TFT module yearlyUSD function throws if passed anything other than a positive value.

✅ discourse.test.ts

 TC2690 - Applications: Deploy Discourse
  ⚪ TC2690 - Applications: Deploy Discourse

✅ funkwhale.test.ts

 TC2685 - Applications: Deploy Funkwhale
  ✅ TC2685 - Applications: Deploy Funkwhale

❌ gateways.test.ts

 TC1237 - Gateways: Expose a VM Over Gateway
  ❌ TC1237 - Gateways: Expose a VM Over Gateway
	Error: Gateway is unreachable after multiple retries

❌ kubernetes.test.ts

 TC1231 - Kubernetes: Deploy a Kubernetes Cluster
  ❌ TC1231 - Kubernetes: Deploy a Kubernetes Cluster
	Error: expect(received).toHaveLength(expected)
 TC1232 - Kubernetes: Add Worker
  ❌ TC1232 - Kubernetes: Add Worker
	Error: expect(received).toHaveLength(expected)
 TC1233 - Kubernetes: Delete Worker
  ❌ TC1233 - Kubernetes: Delete Worker
	Error: expect(received).toHaveLength(expected)

✅ kvstore.test.ts

 TC1238 - KVStore: Use TFChain KVStore
  ✅ TC1238 - KVStore: Use TFChain KVStore

✅ mattermost.test.ts

 TC2689 - Applications: Deploy Mattermost
  ✅ TC2689 - Applications: Deploy Mattermost

✅ network_light.test.ts

NetworkLight Class Tests should create a valid NetworkLight instance
  ✅ NetworkLight Class Tests should create a valid NetworkLight instance
NetworkLight Class Tests should correctly serialize and deserialize a NetworkLight instance
  ✅ NetworkLight Class Tests should correctly serialize and deserialize a NetworkLight instance
NetworkLight Class Tests should correctly compute the challenge string
  ✅ NetworkLight Class Tests should correctly compute the challenge string
NetworkLight Class Tests should correctly handle missing peers
  ✅ NetworkLight Class Tests should correctly handle missing peers
NetworkLight Class Tests should throw an error if subnet is empty
  ✅ NetworkLight Class Tests should throw an error if subnet is empty
NetworkLight Class Tests should handle an empty mycelium object correctly
  ✅ NetworkLight Class Tests should handle an empty mycelium object correctly
NetworkLight Class Tests should correctly handle peers being empty
  ✅ NetworkLight Class Tests should correctly handle peers being empty

✅ nextcloud.test.ts

 TC2692 - Applications: Deploy Nextcloud
  ✅ TC2692 - Applications: Deploy Nextcloud

✅ nodepilot.test.ts

 TC2701 - Applications: Deploy Nodepilot
  ⚪ TC2701 - Applications: Deploy Nodepilot

✅ peertube.test.ts

 TC2684 - Applications: Deploy Peertube
  ✅ TC2684 - Applications: Deploy Peertube

✅ presearch.test.ts

 TC2728 - Applications: Deploy Presearch
  ✅ TC2728 - Applications: Deploy Presearch

❌ qsfs.test.ts

 TC1234 - QSFS: Deploy QSFS underneath a VM
  ❌ TC1234 - QSFS: Deploy QSFS underneath a VM
	Error: thrown: "Exceeded timeout of 300000 ms for a test.
 TC1235 - QSFS: Deploy QSFS Underneath a Kubernetes Cluster
  ❌ TC1235 - QSFS: Deploy QSFS Underneath a Kubernetes Cluster
	Error: Failed to deploy qsfs with name jtfmlo1xzqh04sh on node 166 due to: failed to create qsfs mount: failed to prepare qsfs: failed to create ygg link: peer already exists "p-ygg0".

✅ query_to_string.test.ts

Convert object to query string should return an empty string when given an empty object
  ✅ Convert object to query string should return an empty string when given an empty object
Convert object to query string should correctly convert an object with string values to a query string
  ✅ Convert object to query string should correctly convert an object with string values to a query string
Convert object to query string should correctly convert an object with number values to a query string
  ✅ Convert object to query string should correctly convert an object with number values to a query string
Convert object to query string should correctly convert an object with mixed types of values to a query string
  ✅ Convert object to query string should correctly convert an object with mixed types of values to a query string
Convert object to query string should filter out undefined values from the object
  ✅ Convert object to query string should filter out undefined values from the object
Convert object to query string should filter out empty string values from the object
  ✅ Convert object to query string should filter out empty string values from the object

✅ root_fs.test.ts

Calculate the rootFS size based on the machine specs should return 2GB when the options are provided
  ✅ Calculate the rootFS size based on the machine specs should return 2GB when the options are provided
Calculate the rootFS size based on the machine specs should return 0.48828125 when CPU cores and RAM are zero
  ✅ Calculate the rootFS size based on the machine specs should return 0.48828125 when CPU cores and RAM are zero

✅ stellar.test.ts

 TC1254 - Stellar: Create Account
  ✅ TC1254 - Stellar: Create Account
 TC1255 - Stellar: Import Account
  ✅ TC1255 - Stellar: Import Account
 TC1256 - Stellar: Get Account
  ✅ TC1256 - Stellar: Get Account
 TC1257 - Stellar: Check if Account exists
  ✅ TC1257 - Stellar: Check if Account exists
 TC1258 - Stellar: List Accounts
  ✅ TC1258 - Stellar: List Accounts
 TC1259 - Stellar: Get Account assets
  ✅ TC1259 - Stellar: Get Account assets
 TC1260 - Stellar: Get Account assets by address
  ✅ TC1260 - Stellar: Get Account assets by address

✅ subsquid.test.ts

 TC2693 - Applications: Deploy Subsquid
  ✅ TC2693 - Applications: Deploy Subsquid

✅ taiga.test.ts

 TC2691 - Applications: Deploy Taiga
  ✅ TC2691 - Applications: Deploy Taiga

✅ tfchain.test.ts

 TC1261 - TFChain: Create Account
  ✅ TC1261 - TFChain: Create Account
 TC1262 - TFChain: Import Account
  ✅ TC1262 - TFChain: Import Account
 TC1263 - TFChain: Get Account
  ✅ TC1263 - TFChain: Get Account
 TC1264 - TFChain: Check if Account exists
  ✅ TC1264 - TFChain: Check if Account exists
 TC1265 - TFChain: List Accounts
  ✅ TC1265 - TFChain: List Accounts
 TC1266 - TFChain: Get Account assets
  ✅ TC1266 - TFChain: Get Account assets
 TC1267 - TFChain: Get Account assets by address
  ✅ TC1267 - TFChain: Get Account assets by address
 TC1268 - TFChain: Transfer TFTs
  ✅ TC1268 - TFChain: Transfer TFTs

✅ umbrel.test.ts

 TC2694 - Applications: Deploy Umbrel
  ✅ TC2694 - Applications: Deploy Umbrel

❌ vm.test.ts

 TC1228 - VM: Deploy a VM
  ✅ TC1228 - VM: Deploy a VM
 TC2847 - VM: Deploy a VM With Mycelium
  ❌ TC2847 - VM: Deploy a VM With Mycelium
	Error: expect(received).toContain(expected) // indexOf
 TC1229 - VM: Deploy a VM With a Disk
  ✅ TC1229 - VM: Deploy a VM With a Disk
 TC1230 - VM: Deploy Multiple VMs on Different Nodes
  ✅ TC1230 - VM: Deploy Multiple VMs on Different Nodes

✅ volume.test.ts

Test volume workload. volume should be type of Volume
  ✅ Test volume workload. volume should be type of Volume
Test volume workload. should fail if passed invalid size
  ✅ Test volume workload. should fail if passed invalid size
Test volume workload. should fail if volume was assigned to an invalid parsed obj
  ✅ Test volume workload. should fail if volume was assigned to an invalid parsed obj

✅ wordpress.test.ts

 TC2700 - Applications: Deploy Wordpress
  ✅ TC2700 - Applications: Deploy Wordpress

✅ workload.test.ts

Workload Tests for zmachine should create a valid Workload instance
  ✅ Workload Tests for zmachine should create a valid Workload instance
Workload Tests for zmachine should handle valid Workload properties
  ✅ Workload Tests for zmachine should handle valid Workload properties
Workload Tests for zmachine should correctly serialize and deserialize Workload
  ✅ Workload Tests for zmachine should correctly serialize and deserialize Workload
Workload Tests for zmachine should correctly compute the challenge string
  ✅ Workload Tests for zmachine should correctly compute the challenge string
Workload Tests for zmachine should handle invalid DeploymentResult
  ✅ Workload Tests for zmachine should handle invalid DeploymentResult
Workload Tests for zmount should create a valid Workload instance
  ✅ Workload Tests for zmount should create a valid Workload instance
Workload Tests for zmount should handle valid Workload properties
  ✅ Workload Tests for zmount should handle valid Workload properties
Workload Tests for zmount should correctly serialize and deserialize Workload
  ✅ Workload Tests for zmount should correctly serialize and deserialize Workload
Workload Tests for zmount should correctly compute the challenge string
  ✅ Workload Tests for zmount should correctly compute the challenge string
Workload Tests for zmount should handle invalid DeploymentResult
  ✅ Workload Tests for zmount should handle invalid DeploymentResult
Workload Tests for volume should create a valid Workload instance
  ✅ Workload Tests for volume should create a valid Workload instance
Workload Tests for volume should handle valid Workload properties
  ✅ Workload Tests for volume should handle valid Workload properties
Workload Tests for volume should correctly serialize and deserialize Workload
  ✅ Workload Tests for volume should correctly serialize and deserialize Workload
Workload Tests for volume should correctly compute the challenge string
  ✅ Workload Tests for volume should correctly compute the challenge string
Workload Tests for volume should handle invalid DeploymentResult
  ✅ Workload Tests for volume should handle invalid DeploymentResult
Workload Tests for network should create a valid Workload instance
  ✅ Workload Tests for network should create a valid Workload instance
Workload Tests for network should handle valid Workload properties
  ✅ Workload Tests for network should handle valid Workload properties
Workload Tests for network should correctly serialize and deserialize Workload
  ✅ Workload Tests for network should correctly serialize and deserialize Workload
Workload Tests for network should correctly compute the challenge string
  ✅ Workload Tests for network should correctly compute the challenge string
Workload Tests for network should handle invalid DeploymentResult
  ✅ Workload Tests for network should handle invalid DeploymentResult
Workload Tests for zdb should create a valid Workload instance
  ✅ Workload Tests for zdb should create a valid Workload instance
Workload Tests for zdb should handle valid Workload properties
  ✅ Workload Tests for zdb should handle valid Workload properties
Workload Tests for zdb should correctly serialize and deserialize Workload
  ✅ Workload Tests for zdb should correctly serialize and deserialize Workload
Workload Tests for zdb should correctly compute the challenge string
  ✅ Workload Tests for zdb should correctly compute the challenge string
Workload Tests for zdb should handle invalid DeploymentResult
  ✅ Workload Tests for zdb should handle invalid DeploymentResult
Workload Tests for ipv4 should create a valid Workload instance
  ✅ Workload Tests for ipv4 should create a valid Workload instance
Workload Tests for ipv4 should handle valid Workload properties
  ✅ Workload Tests for ipv4 should handle valid Workload properties
Workload Tests for ipv4 should correctly serialize and deserialize Workload
  ✅ Workload Tests for ipv4 should correctly serialize and deserialize Workload
Workload Tests for ipv4 should correctly compute the challenge string
  ✅ Workload Tests for ipv4 should correctly compute the challenge string
Workload Tests for ipv4 should handle invalid DeploymentResult
  ✅ Workload Tests for ipv4 should handle invalid DeploymentResult
Workload Tests for ip should create a valid Workload instance
  ✅ Workload Tests for ip should create a valid Workload instance
Workload Tests for ip should handle valid Workload properties
  ✅ Workload Tests for ip should handle valid Workload properties
Workload Tests for ip should correctly serialize and deserialize Workload
  ✅ Workload Tests for ip should correctly serialize and deserialize Workload
Workload Tests for ip should correctly compute the challenge string
  ✅ Workload Tests for ip should correctly compute the challenge string
Workload Tests for ip should handle invalid DeploymentResult
  ✅ Workload Tests for ip should handle invalid DeploymentResult
Workload Tests for gateway-fqdn-proxy should create a valid Workload instance
  ✅ Workload Tests for gateway-fqdn-proxy should create a valid Workload instance
Workload Tests for gateway-fqdn-proxy should handle valid Workload properties
  ✅ Workload Tests for gateway-fqdn-proxy should handle valid Workload properties
Workload Tests for gateway-fqdn-proxy should correctly serialize and deserialize Workload
  ✅ Workload Tests for gateway-fqdn-proxy should correctly serialize and deserialize Workload
Workload Tests for gateway-fqdn-proxy should correctly compute the challenge string
  ✅ Workload Tests for gateway-fqdn-proxy should correctly compute the challenge string
Workload Tests for gateway-fqdn-proxy should handle invalid DeploymentResult
  ✅ Workload Tests for gateway-fqdn-proxy should handle invalid DeploymentResult
Workload Tests for gateway-name-proxy should create a valid Workload instance
  ✅ Workload Tests for gateway-name-proxy should create a valid Workload instance
Workload Tests for gateway-name-proxy should handle valid Workload properties
  ✅ Workload Tests for gateway-name-proxy should handle valid Workload properties
Workload Tests for gateway-name-proxy should correctly serialize and deserialize Workload
  ✅ Workload Tests for gateway-name-proxy should correctly serialize and deserialize Workload
Workload Tests for gateway-name-proxy should correctly compute the challenge string
  ✅ Workload Tests for gateway-name-proxy should correctly compute the challenge string
Workload Tests for gateway-name-proxy should handle invalid DeploymentResult
  ✅ Workload Tests for gateway-name-proxy should handle invalid DeploymentResult
Workload Tests for qsfs should create a valid Workload instance
  ✅ Workload Tests for qsfs should create a valid Workload instance
Workload Tests for qsfs should handle valid Workload properties
  ✅ Workload Tests for qsfs should handle valid Workload properties
Workload Tests for qsfs should correctly serialize and deserialize Workload
  ✅ Workload Tests for qsfs should correctly serialize and deserialize Workload
Workload Tests for qsfs should correctly compute the challenge string
  ✅ Workload Tests for qsfs should correctly compute the challenge string
Workload Tests for qsfs should handle invalid DeploymentResult
  ✅ Workload Tests for qsfs should handle invalid DeploymentResult
Workload Tests for zlogs should create a valid Workload instance
  ✅ Workload Tests for zlogs should create a valid Workload instance
Workload Tests for zlogs should handle valid Workload properties
  ✅ Workload Tests for zlogs should handle valid Workload properties
Workload Tests for zlogs should correctly serialize and deserialize Workload
  ✅ Workload Tests for zlogs should correctly serialize and deserialize Workload
Workload Tests for zlogs should correctly compute the challenge string
  ✅ Workload Tests for zlogs should correctly compute the challenge string
Workload Tests for zlogs should handle invalid DeploymentResult
  ✅ Workload Tests for zlogs should handle invalid DeploymentResult
Workload Tests for network-light should create a valid Workload instance
  ✅ Workload Tests for network-light should create a valid Workload instance
Workload Tests for network-light should handle valid Workload properties
  ✅ Workload Tests for network-light should handle valid Workload properties
Workload Tests for network-light should correctly serialize and deserialize Workload
  ✅ Workload Tests for network-light should correctly serialize and deserialize Workload
Workload Tests for network-light should correctly compute the challenge string
  ✅ Workload Tests for network-light should correctly compute the challenge string
Workload Tests for network-light should handle invalid DeploymentResult
  ✅ Workload Tests for network-light should handle invalid DeploymentResult
Workload Tests for zmachine-light should create a valid Workload instance
  ✅ Workload Tests for zmachine-light should create a valid Workload instance
Workload Tests for zmachine-light should handle valid Workload properties
  ✅ Workload Tests for zmachine-light should handle valid Workload properties
Workload Tests for zmachine-light should correctly serialize and deserialize Workload
  ✅ Workload Tests for zmachine-light should correctly serialize and deserialize Workload
Workload Tests for zmachine-light should correctly compute the challenge string
  ✅ Workload Tests for zmachine-light should correctly compute the challenge string
Workload Tests for zmachine-light should handle invalid DeploymentResult
  ✅ Workload Tests for zmachine-light should handle invalid DeploymentResult

✅ zdb.test.ts

 TC1236 - ZDB: Deploy ZDBs
  ✅ TC1236 - ZDB: Deploy ZDBs

✅ zmachine_light.test.ts

ZmachineLight Class Tests should create a valid ZmachineLight instance
  ✅ ZmachineLight Class Tests should create a valid ZmachineLight instance
ZmachineLight Class Tests should correctly serialize and deserialize a ZmachineLight instance
  ✅ ZmachineLight Class Tests should correctly serialize and deserialize a ZmachineLight instance
ZmachineLight Class Tests should correctly handle env vars
  ✅ ZmachineLight Class Tests should correctly handle env vars
ZmachineLight Class Tests should correctly compute the challenge string
  ✅ ZmachineLight Class Tests should correctly compute the challenge string
ZmachineLight Class Tests should correctly handle the gpu array
  ✅ ZmachineLight Class Tests should correctly handle the gpu array
ZmachineLight Class Tests should fail validation for entering invalid flist
  ✅ ZmachineLight Class Tests should fail validation for entering invalid flist
ZmachineLight Class Tests should fail validation for entering invalid entrypoint
  ✅ ZmachineLight Class Tests should fail validation for entering invalid entrypoint
ZmachineLight Class Tests should fail validation for entering invalid size
  ✅ ZmachineLight Class Tests should fail validation for entering invalid size
ZmachineLight Class Tests should throw error if network interfaces values are invalid
  ✅ ZmachineLight Class Tests should throw error if network interfaces values are invalid
ZmachineLight Class Tests should throw an error if mount name is empty
  ✅ ZmachineLight Class Tests should throw an error if mount name is empty
ZmachineLight Class Tests should fail if zmachineLight is parsed to an invalid object
  ✅ ZmachineLight Class Tests should fail if zmachineLight is parsed to an invalid object

✅ zmachine.test.ts

Zmachine Class Tests should create a valid Zmachine instance
  ✅ Zmachine Class Tests should create a valid Zmachine instance
Zmachine Class Tests should correctly serialize and deserialize a Zmachine instance
  ✅ Zmachine Class Tests should correctly serialize and deserialize a Zmachine instance
Zmachine Class Tests should correctly handle env vars
  ✅ Zmachine Class Tests should correctly handle env vars
Zmachine Class Tests should correctly compute the challenge string
  ✅ Zmachine Class Tests should correctly compute the challenge string
Zmachine Class Tests should correctly handle the gpu array
  ✅ Zmachine Class Tests should correctly handle the gpu array
Zmachine Class Tests should fail validation for entering invalid flist
  ✅ Zmachine Class Tests should fail validation for entering invalid flist
Zmachine Class Tests should fail validation for entering invalid entrypoint
  ✅ Zmachine Class Tests should fail validation for entering invalid entrypoint
Zmachine Class Tests should fail validation for entering invalid size
  ✅ Zmachine Class Tests should fail validation for entering invalid size
Zmachine Class Tests should throw error if network public_ip is invalid
  ✅ Zmachine Class Tests should throw error if network public_ip is invalid
Zmachine Class Tests should throw error if network interfaces values are invalid
  ✅ Zmachine Class Tests should throw error if network interfaces values are invalid
Zmachine Class Tests should throw an error if mount name is empty
  ✅ Zmachine Class Tests should throw an error if mount name is empty
Zmachine Class Tests should fail if zmachine is parsed to an invalid object
  ✅ Zmachine Class Tests should fail if zmachine is parsed to an invalid object

✅ zmount.test.ts

Zmount Class Initialization should be initialized with default values
  ✅ Zmount Class Initialization should be initialized with default values
Zmount Class size property validation should fail validation if size is set to a non-numeric value
  ✅ Zmount Class size property validation should fail validation if size is set to a non-numeric value
Zmount Class size property validation should fail validation if size is null
  ✅ Zmount Class size property validation should fail validation if size is null
Zmount Class size property validation should fail validation if size is undefined
  ✅ Zmount Class size property validation should fail validation if size is undefined
Zmount Class size property validation should fail validation if size is less than the minimum
  ✅ Zmount Class size property validation should fail validation if size is less than the minimum
Zmount Class size property validation should fail validation if size is greater than the maximum
  ✅ Zmount Class size property validation should fail validation if size is greater than the maximum
Zmount Class size property validation should pass validation if size is a valid number within the range
  ✅ Zmount Class size property validation should pass validation if size is a valid number within the range
Zmount Class challenge method should return the size as a string
  ✅ Zmount Class challenge method should return the size as a string

Annotations

Check failure on line 75 in packages/grid_client/tests/modules/gateways.test.ts

See this annotation in the file changed.

@github-actions github-actions / JEST Tests

gateways.test.ts ► TC1237 - Gateways: Expose a VM Over Gateway ► TC1237 - Gateways: Expose a VM Over Gateway 

Failed test found in:
  packages/grid_client/tests/test-reports/report.xml
Error:
  Error: Gateway is unreachable after multiple retries
Raw output 
Error: Gateway is unreachable after multiple retries
    at testGateway (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/tests/modules/gateways.test.ts:75:11)
    at Object.<anonymous> (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/tests/modules/gateways.test.ts:242:3)

Check failure on line 193 in packages/grid_client/tests/modules/kubernetes.test.ts

See this annotation in the file changed.

@github-actions github-actions / JEST Tests

kubernetes.test.ts ► TC1231 - Kubernetes: Deploy a Kubernetes Cluster ► TC1231 - Kubernetes: Deploy a Kubernetes Cluster 

Failed test found in:
  packages/grid_client/tests/test-reports/report.xml
Error:
  Error: expect(received).toHaveLength(expected)
Raw output 
Error: expect(received).toHaveLength(expected)

Expected length: 2
Received length: 1
Received array:  [{"contractId": 189162, "contractType": {"nodeContract": {"deploymentData": "{\"version\":3,\"type\":\"kubernetes\",\"name\":\"dsxiunz4k0ojplb\",\"projectName\":\"kubernetes/dsxiunz4k0ojplb\"}", "deploymentHash": "d5091f8216dc685de233f7640b0b435a", "nodeId": 168, "publicIps": 0, "publicIpsList": []}}, "solutionProviderId": null, "state": {"created": null}, "twinId": 51, "version": 4}]
    at Object.<anonymous> (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/tests/modules/kubernetes.test.ts:193:33)

Check failure on line 480 in packages/grid_client/tests/modules/kubernetes.test.ts

See this annotation in the file changed.

@github-actions github-actions / JEST Tests

kubernetes.test.ts ► TC1232 - Kubernetes: Add Worker ► TC1232 - Kubernetes: Add Worker 

Failed test found in:
  packages/grid_client/tests/test-reports/report.xml
Error:
  Error: expect(received).toHaveLength(expected)
Raw output 
Error: expect(received).toHaveLength(expected)

Expected length: 2
Received length: 1
Received array:  [{"contractId": 189165, "contractType": {"nodeContract": {"deploymentData": "{\"version\":3,\"type\":\"kubernetes\",\"name\":\"81zgfkbtxu11bi8\",\"projectName\":\"kubernetes/81zgfkbtxu11bi8\"}", "deploymentHash": "ebc5fe408ee675bd43ec11a7e784e696", "nodeId": 28, "publicIps": 0, "publicIpsList": []}}, "solutionProviderId": null, "state": {"created": null}, "twinId": 51, "version": 4}]
    at Object.<anonymous> (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/tests/modules/kubernetes.test.ts:480:33)

Check failure on line 730 in packages/grid_client/tests/modules/kubernetes.test.ts

See this annotation in the file changed.

@github-actions github-actions / JEST Tests

kubernetes.test.ts ► TC1233 - Kubernetes: Delete Worker ► TC1233 - Kubernetes: Delete Worker 

Failed test found in:
  packages/grid_client/tests/test-reports/report.xml
Error:
  Error: expect(received).toHaveLength(expected)
Raw output 
Error: expect(received).toHaveLength(expected)

Expected length: 2
Received length: 1
Received array:  [{"contractId": 189167, "contractType": {"nodeContract": {"deploymentData": "{\"version\":3,\"type\":\"kubernetes\",\"name\":\"thk2p2oh0qczgqv\",\"projectName\":\"kubernetes/thk2p2oh0qczgqv\"}", "deploymentHash": "20591cfcc0bc852565e70add8dbdbfe2", "nodeId": 12, "publicIps": 0, "publicIpsList": []}}, "solutionProviderId": null, "state": {"created": null}, "twinId": 51, "version": 4}]
    at Object.<anonymous> (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/tests/modules/kubernetes.test.ts:730:33)

Check failure on line 30 in packages/grid_client/tests/modules/qsfs.test.ts

See this annotation in the file changed.

@github-actions github-actions / JEST Tests

qsfs.test.ts ► TC1234 - QSFS: Deploy QSFS underneath a VM ► TC1234 - QSFS: Deploy QSFS underneath a VM 

Failed test found in:
  packages/grid_client/tests/test-reports/report.xml
Error:
  Error: thrown: "Exceeded timeout of 300000 ms for a test.
Raw output 
Error: thrown: "Exceeded timeout of 300000 ms for a test.
Add a timeout value to this test to increase the timeout, if this is a long-running test. See https://jestjs.io/docs/api#testname-fn-timeout."
    at Object.<anonymous> (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/tests/modules/qsfs.test.ts:30:1)
    at Runtime._execModule (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/node_modules/jest-runtime/build/index.js:1429:24)
    at Runtime._loadModule (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/node_modules/jest-runtime/build/index.js:1013:12)
    at Runtime.requireModule (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/node_modules/jest-runtime/build/index.js:873:12)
    at jestAdapter (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/node_modules/@jest/core/node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:77:13)
    at runTestInternal (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/node_modules/jest-runner/build/runTest.js:367:16)
    at runTest (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/node_modules/jest-runner/build/runTest.js:444:34)

Check failure on line 89 in packages/grid_client/src/high_level/twinDeploymentHandler.ts

See this annotation in the file changed.

@github-actions github-actions / JEST Tests

qsfs.test.ts ► TC1235 - QSFS: Deploy QSFS Underneath a Kubernetes Cluster ► TC1235 - QSFS: Deploy QSFS Underneath a Kubernetes Cluster 

Failed test found in:
  packages/grid_client/tests/test-reports/report.xml
Error:
  Error: Failed to deploy qsfs with name jtfmlo1xzqh04sh on node 166 due to: failed to create qsfs mount: failed to prepare qsfs: failed to create ygg link: peer already exists "p-ygg0".
Raw output 
Error: Failed to deploy qsfs with name jtfmlo1xzqh04sh on node 166 due to: failed to create qsfs mount: failed to prepare qsfs: failed to create ygg link: peer already exists "p-ygg0".
    at TwinDeploymentHandler.checkWorkload (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/src/high_level/twinDeploymentHandler.ts:89:13)
    at TwinDeploymentHandler.checkWorkload [as waitForDeployment] (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/src/high_level/twinDeploymentHandler.ts:116:22)
    at async Promise.all (index 1)
    at TwinDeploymentHandler.handle (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/src/high_level/twinDeploymentHandler.ts:616:7)
    at K8sModule.deploy (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/src/modules/k8s.ts:309:23)
    at K8sModule.descriptor.value (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/src/modules/utils.ts:19:12)
    at Object.<anonymous> (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/tests/modules/qsfs.test.ts:575:15)

Check failure on line 344 in packages/grid_client/tests/modules/vm.test.ts

See this annotation in the file changed.

@github-actions github-actions / JEST Tests

vm.test.ts ► TC2847 - VM: Deploy a VM With Mycelium ► TC2847 - VM: Deploy a VM With Mycelium 

Failed test found in:
  packages/grid_client/tests/test-reports/report.xml
Error:
  Error: expect(received).toContain(expected) // indexOf
Raw output 
Error: expect(received).toContain(expected) // indexOf

Matcher error: received value must not be null nor undefined

Received has value: undefined
    at /home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/tests/modules/vm.test.ts:347:30
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.<anonymous> (/home/runner/work/tfgrid-sdk-ts/tfgrid-sdk-ts/packages/grid_client/tests/modules/vm.test.ts:344:5)
View more details on GitHub Actions