test_warm_after_failed_create_over_max_code_size()¶
Documentation for tests/amsterdam/eip7954_increase_max_contract_size/test_max_code_size.py::test_warm_after_failed_create_over_max_code_size@c74f1a67.
Generate fixtures for these test cases for Amsterdam with:
fill -v tests/amsterdam/eip7954_increase_max_contract_size/test_max_code_size.py::test_warm_after_failed_create_over_max_code_size --fork Amsterdam
Verify the would-be contract address is warm after a CREATE that fails because the returned deploy code exceeds max_code_size.
Unlike pre-validation aborts (insufficient balance, nonce overflow), the address is added to the access list during initcode execution, so the post-RETURN size check rejecting deployment must leave the address warm.
Source code in tests/amsterdam/eip7954_increase_max_contract_size/test_max_code_size.py
274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 | |
Parametrized Test Cases¶
This test generates 2 parametrized test cases across 1 fork.