Skip to content

roachtest: django failed #90019

@cockroach-teamcity

Description

@cockroach-teamcity

roachtest.django failed with artifacts on release-22.2.0 @ 05ac3556ba72810f2b01558077e4d24e4b244e76:

test artifacts and logs in: /artifacts/django/run_1
	orm_helpers.go:191,orm_helpers.go:117,django.go:217,django.go:228,test_runner.go:930: 
		Tests run on Cockroach v22.2.0-beta.3-89-g05ac3556ba
		Tests run against django cockroach-4.1.x
		9935 Total Tests Run
		9934 tests passed
		1 test failed
		646 tests skipped
		2 tests ignored
		0 tests passed unexpectedly
		1 test failed unexpectedly
		0 tests expected failed but skipped
		0 tests expected failed but not run
		---
		--- SKIP: backends.mysql.test_creation.DatabaseCreationTests.test_create_test_db_unexpected_error due to MySQL tests (expected)
		--- FAIL: select_for_update.tests.SelectForUpdateTests.test_raw_lock_not_available (unexpected)
		For a full summary look at the django artifacts 
		
		An updated blocklist (djangoBlocklist) is available in the artifacts' django log

Parameters: ROACHTEST_cloud=gce , ROACHTEST_cpu=16 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

/cc @cockroachdb/sql-experience

This test on roachdash | Improve this report!

Jira issue: CRDB-20547

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-test-failureBroken test (automatically or manually discovered).O-roachtestO-robotOriginated from a bot.T-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions