Related to the managed access tickets: ebi-ait/dcp-ingest-central#967 & ebi-ait/dcp-ingest-central#1012
During testing the managed access changes I noticed a problem when running several integration tests in parallel where one or more might fail, but when later run sequentially the would all pass.
In order to make sure that this is not due to a problem with the integration tests I ran a similar scenario using only API calls in postman and command line calls of hca-util.
Scenario:
run twice the /api_upload end point to upload a spreadsheet.
The logs show that the failing submission does not start validation of its metadata documents. Furthermore, the failing submission does not have its project short name updated. See screenshot:
In order to prevent two simultaneous spreadsheet upload during the integration tests, I am going to add a random pause of between 5 and 15 seconds before starting each gitlab job:
Related to the managed access tickets: ebi-ait/dcp-ingest-central#967 & ebi-ait/dcp-ingest-central#1012
During testing the managed access changes I noticed a problem when running several integration tests in parallel where one or more might fail, but when later run sequentially the would all pass. In order to make sure that this is not due to a problem with the integration tests I ran a similar scenario using only API calls in postman and command line calls of hca-util.
Scenario:
/api_upload
end point to upload a spreadsheet.METADATA_INVALID
as it should.PENDING
, which is a bug.Example submissions:
See diff of logs: Logs from 2 Submissions in Parallel - 20240715 - one failure.pdf
The logs show that the failing submission does not start validation of its metadata documents. Furthermore, the failing submission does not have its project short name updated. See screenshot: