Skip to content

increase memory limits for lexbox api, 1gb for prod #708

increase memory limits for lexbox api, 1gb for prod

increase memory limits for lexbox api, 1gb for prod #708

GitHub Actions / Integration Tests windows-latest for Mercurial 6 failed Aug 26, 2024 in 0s

1 fail, 1 skipped, 49 pass in 25s

51 tests   - 25   49 ✅  - 23   25s ⏱️ - 19m 49s
 1 suites  -  1    1 💤 ± 0 
 1 files    -  1    1 ❌  -  2 

Results for commit be49586. ± Comparison against earlier commit f23bc27.

Annotations

Check warning on line 0 in Testing.ApiTests.ResetPojectRaceCondition

See this annotation in the file changed.

@github-actions github-actions / Integration Tests windows-latest for Mercurial 6

SimultaneousResetsDontResultIn404s (Testing.ApiTests.ResetPojectRaceCondition) failed

./test-results\runneradmin_fv-az1347-302_2024-08-26_04_32_09.trx [took 6s]
Raw output
System.Net.Http.HttpRequestException : Response status code does not indicate success: 502 (Bad Gateway).   at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
   at Testing.Services.LexboxProject.DisposeAsync() in D:\a\languageforge-lexbox\languageforge-lexbox\backend\Testing\Services\Utils.cs:line 116
   at Testing.ApiTests.ResetPojectRaceCondition.SimultaneousResetsDontResultIn404s() in D:\a\languageforge-lexbox\languageforge-lexbox\backend\Testing\ApiTests\ResetProjectRaceConditions.cs:line 64
--- End of stack trace from previous location ---