You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Latelly we have had integration of the simtel_array data analysis in digicampipe. And in the near future we will have files from the camera calibration.
So far we are unit-testing but with cron jobs from TravisCI we can try to schedule more complete tests.
The issue right now are:
Time limitation by TravisCI
Limited space inside the repo.
Regarding those points
The timeout is:
A job produces no log output for 10 minutes
A job on travis-ci.org takes longer than 50 minutes
No idea what is the limit for Travis (assume same as GH)
So it seems not a solution to run these kind of tests with TravisCI in the long term. But I believe one can ask Travis to trigger some jobs on a machine/cluster of machines that has access to the MC and data files.
Any suggestions?
The text was updated successfully, but these errors were encountered:
Yes I think the plan is to use a machine that has already access to the "database". That would be even better if it is a machine we are already familiar with (one of the cluster we use, or a cluster that we will use).
Latelly we have had integration of the simtel_array data analysis in digicampipe. And in the near future we will have files from the camera calibration.
So far we are unit-testing but with cron jobs from TravisCI we can try to schedule more complete tests.
The issue right now are:
Regarding those points
(https://docs.travis-ci.com/user/customizing-the-build/#Build-Timeouts)
So it seems not a solution to run these kind of tests with TravisCI in the long term. But I believe one can ask Travis to trigger some jobs on a machine/cluster of machines that has access to the MC and data files.
Any suggestions?
The text was updated successfully, but these errors were encountered: