Skip to content

fix: handle nullable values by printing NULL instead of panicking #4565

fix: handle nullable values by printing NULL instead of panicking

fix: handle nullable values by printing NULL instead of panicking #4565

MariaDB (10_4, tokio, native-tls)

succeeded Jan 15, 2025 in 8m 1s
Set up job
0s
Run actions/checkout@v4
1s
Run Swatinem/rust-cache@v2
16s
Run cargo build --features mysql,_unstable-all-types,runtime-tokio,tls-native-tls
37s
Run docker compose -f tests/docker-compose.yml run -d -p 3306:3306 --name mariadb_10_4 mariadb_10_4
7s
Run sleep 30
30s
Run mkdir .sqlx
0s
Run cargo test --no-default-features --features any,mysql,macros,_unstable-all-types,runtime-tokio,tls-native-tls
2m 4s
Run cargo clean -p sqlx
3s
Run cargo build --no-default-features --test mysql-macros --features any,mysql,macros,_unstable-all-types,runtime-tokio,tls-native-tls
1m 8s
Run cargo test --no-default-features --test mysql-macros --features any,mysql,macros,_unstable-all-types,runtime-tokio,tls-native-tls
1m 7s
Run docker stop mariadb_10_4
1m 6s
Run cargo test --no-default-features --features any,mysql,macros,_unstable-all-types,runtime-tokio,tls-native-tls
58s
Post Run Swatinem/rust-cache@v2
0s
Post Run actions/checkout@v4
0s
Complete job
1s