How to resolve deadlock (waiting for signal of failed test)
php editor Xiaoxin will introduce to you how to solve the deadlock problem. Deadlock is a common problem in concurrent programming. Deadlock occurs when two or more processes wait for each other to release resources. In order to solve this problem, we can use some common methods, such as using mutex locks, avoiding resource competition, using timeout mechanisms, etc. Through reasonable design and adjustment, we can effectively avoid the occurrence of deadlock and improve the concurrency and stability of the program. Next, let’s take a closer look at how to solve the deadlock problem!
Question content
I have two goroutines, which are two testxxx functions during testing. I use condition variables to synchronize these goroutines. However, once one of the tests fails, the other one is waiting for a signal. The deadlock is coming. Also, if testfunctionb fails, I want testfunctiona to fail too.
var cond sync.cond func testfunctiona(t *testing.t){ // ... some codes... cond.wait() } func testfunctionb(t *testing.t){ // ... some codes... t.fail() // ... some codes... cond.broadcast() }
I have tried some methods, such as:
var cond sync.Cond var A_t *testing.T func TestFunctionA(t *testing.T){ // ... Some codes... A_t = t // ... Some codes... cond.Wait() } func TestFunctionB(t *testing.T){ // ... Some codes... t.Cleanup(func(){ if !A_t.Failed(){ A_t.Fail() } cond.Broadcast() }) t.Fail() // ... Some codes... cond.Broadcast() }
But when functionb has no errors, a_t.fail() will still be triggered.
I am also considering using context.context(). However, I don't know how to run the test function within the context. Thank you for reading my question! I appreciate any comments or discussion!
Workaround
One test should not interact with another test. However, when using subtests we can share anything between test cases.
Here is an example:
package main import ( "errors" "testing" ) func TestFruits(t *testing.T) { var err error t.Run("test apple", getTestAppleFunc(&err)) t.Run("test banana", getTestBananaFunc(&err)) } func handleError(t *testing.T, err *error) { if err != nil && *err != nil { t.Error(*err) } } func getTestAppleFunc(err *error) func(*testing.T) { return func(t *testing.T) { handleError(t, err) *err = errors.New("Apple failed") } } func getTestBananaFunc(err *error) func(*testing.T) { return func(t *testing.T) { handleError(t, err) } }
- In the functions
gettestbananafunc
andgettestapplefunc
, the error pointer is passed as a parameter. - In the above example, the first execution is
gettestapplefunc
. - If there is an incorrect assignment in
gettestapplefunc
(as in the example above), thegettestbananafunc
function will fail.
The above is the detailed content of How to resolve deadlock (waiting for signal of failed test). For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...
