Failes sometimes on GitHub Actions

[Aleksandra-Omegapoint]

I am getting intermittent failures when running my integration-tests using a MsSql test container in github actions. I don't have these issues when I run on my own computer, and sometimes they work on github as well. I don't know how I would go about debugging this.

The issues are either

2025-03-05T15:17:22.3614254Z   Error Message:
2025-03-05T15:17:22.3633197Z    Docker.DotNet.DockerApiException : Docker API responded with status code=Conflict, response={"message":"container 91a7ef569bb1c7a052902a4fff0ac7b68eb690899f0c793149ef21839b6648b1 is not running"}

or

2025-03-05T15:18:17.3180451Z   Error Message:
2025-03-05T15:18:17.3200559Z    Microsoft.Data.SqlClient.SqlException : A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - Success)

On my own computer I have to limit xUnit's max threads, if not I get issues with docker (and my computer stalls). I tried setting the maxThreads to 1 for GitHub actions hoping that would help, but it doesn't seem to.

The fixtures are set up as follows:

public class DatabaseFixture : IAsyncLifetime
{
    private readonly MsSqlContainer _msSqlContainer = new MsSqlBuilder().Build();

    public async Task InitializeAsync() { await _msSqlContainer.StartAsync(); }

    public async Task DisposeAsync() { await _msSqlContainer.DisposeAsync(); }

    public string GetConnectionString() => _msSqlContainer.GetConnectionString();
}

Which is passed to a larger test fixture

/// <summary>
///     Test fixture for integration tests that has an empty MsSql database besides a couple of users.
/// </summary>
public class IntegrationTestFixture : IAsyncLifetime
{
    private readonly DatabaseFixture _databaseFixture;
    protected readonly CustomWebApplicationFactory AppFactory;

    public readonly List<User> Users = TestUsers.GetUsers().ToList();

    public IntegrationTestFixture()
    {
        _databaseFixture = new();
        AppFactory = new(_databaseFixture);
    }

    public virtual async Task InitializeAsync()
    {
        await _databaseFixture.InitializeAsync();

        await using var scope = AppFactory.Services.CreateAsyncScope();
        var dbContext = scope.ServiceProvider.GetRequiredService<AppDbContext>();

        await dbContext.Database.EnsureCreatedAsync();

        if (await dbContext.Users.AnyAsync(x => x.Id == Users[0].Id))
            return;

        await dbContext.Users.AddRangeAsync(Users);
        await dbContext.SaveChangesAsync();
    }

    public virtual async Task DisposeAsync()
    {
        await _databaseFixture.DisposeAsync();
        await AppFactory.DisposeAsync();
    }
}

Which is then passed to unit tests through an IClassFixture in xUnit.

[HofmeisterAn]

This configuration looks a bit unusual. How do you configure and set up your database context? I recommend a setup similar to our example:

• Use xUnit.net's class fixture (if you want a single database instance).
• Configure the database connection string using settings (see: Set Redis connection string).

[Aleksandra-Omegapoint]

I think you might have pointed me to the right direction. I was already using class fixtures, the issue was that I was seeding the database using the dbContext in the InitializeAsync. Since the WebApplicationBuilder hasn't been requested to make anything before then, the services (including the database context) wasn't set up, and I probably had a race-condition, which is why it only failed sometimes.