Skip to content

copy_store_data_sync for NftTransferHistoryTable migration #4684

copy_store_data_sync for NftTransferHistoryTable migration

copy_store_data_sync for NftTransferHistoryTable migration #4684

Triggered via push September 15, 2024 09:07
Status Cancelled
Total duration 4m 53s
Artifacts

dev-build.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

17 errors and 1 warning
wasm
Process completed with exit code 1.
android-aarch64
Canceling since a higher priority waiting request for 'Development builds-refs/heads/fix-nft-tx-history-primkey' exists
android-aarch64
The operation was canceled.
linux-x86-64
Canceling since a higher priority waiting request for 'Development builds-refs/heads/fix-nft-tx-history-primkey' exists
linux-x86-64
The operation was canceled.
android-armv7
Canceling since a higher priority waiting request for 'Development builds-refs/heads/fix-nft-tx-history-primkey' exists
android-armv7
The operation was canceled.
win-x86-64
Canceling since a higher priority waiting request for 'Development builds-refs/heads/fix-nft-tx-history-primkey' exists
win-x86-64
The operation was canceled.
mac-x86-64
Canceling since a higher priority waiting request for 'Development builds-refs/heads/fix-nft-tx-history-primkey' exists
mac-x86-64
The operation was canceled.
mac-arm64
Canceling since a higher priority waiting request for 'Development builds-refs/heads/fix-nft-tx-history-primkey' exists
mac-arm64
The operation was canceled.
mac-dylib-x86-64
Canceling since a higher priority waiting request for 'Development builds-refs/heads/fix-nft-tx-history-primkey' exists
mac-dylib-x86-64
The operation was canceled.
ios-aarch64
Canceling since a higher priority waiting request for 'Development builds-refs/heads/fix-nft-tx-history-primkey' exists
ios-aarch64
The operation was canceled.
wasm
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/