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
IMPORTANT: This issue is a companion to #970. I understand that it is about an old version of CMS, but I am reporting it just because maybe some other users will come across it. I do not expect this to be backported.
Description:
The dataset is not reimported when cmsImportTask -u
Steps to reproduce:
Import a task in CMS and attach it to a contest.
Modify your reference solution.
From the task directory, run cmsMake -c
From the task directory, run cmsMake -a
From the task directory, run cmsImportTask [-L italy_yaml] -u -c CONTEST_ID .
Expected:
The new version of the dataset (i.e. the input and output files) gets uploaded to the contest.
Actual:
The contest is still using the old version of the dataset.
A workaround is updating the dataset through the admin interface.
Logs
No relevant logs.
System Information
CMS version:1.3.1 Was CMS installed: yes Using a virtualenv: no Postgres version: 9.3.18 Distribution and version: Ubuntu 16.04.4 LTS (xenial)
The text was updated successfully, but these errors were encountered:
IMPORTANT: This issue is a companion to #970. I understand that it is about an old version of CMS, but I am reporting it just because maybe some other users will come across it. I do not expect this to be backported.
Description:
The dataset is not reimported when
cmsImportTask -u
Steps to reproduce:
cmsMake -c
cmsMake -a
cmsImportTask [-L italy_yaml] -u -c CONTEST_ID .
Expected:
The new version of the dataset (i.e. the input and output files) gets uploaded to the contest.
Actual:
The contest is still using the old version of the dataset.
A workaround is updating the dataset through the admin interface.
Logs
No relevant logs.
System Information
CMS version:
1.3.1
Was CMS installed: yes
Using a virtualenv: no
Postgres version: 9.3.18
Distribution and version: Ubuntu 16.04.4 LTS (xenial)
The text was updated successfully, but these errors were encountered: