-
Notifications
You must be signed in to change notification settings - Fork 164
pipeline/task_spec_test.py is broken #75
Comments
Yeah it relies on files that are generated by the regtest. Probably the simplest fix is to make test.sh run that first, and do document in task_spec_test.py that it relies on the stuff that test.sh creates. It's the same thing as bin/test.sh running write-assoc-testdata basically. |
how to do so? I still dont understand how to fix the problem.... |
You have the wrong address.
…On Sat, Dec 18, 2021 at 9:58 PM tristanwong1188 ***@***.***> wrote:
Yeah it relies on files that are generated by the regtest. Probably the
simplest fix is to make test.sh run that first, and do document in
task_spec_test.py that it relies on the stuff that test.sh creates.
It's the same thing as bin/test.sh running write-assoc-testdata basically.
how to do so?
I still dont understand how to fix the problem....
I only obtain 2015-12-01 folder, but nothing inside the
folder.......emmmmmmmmmmmm....
—
Reply to this email directly, view it on GitHub
<#75 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQPKEU6SVJ6RJR33ZT43ARDURVQ7FANCNFSM4B23FSEQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
And I also have the demo 3 file, but demo 1 and 2..... |
pipeline/task_spec_test.py depends on the existence of the files:
_tmp/counts/2015-12-01/exp_counts.csv
_tmp/counts/2015-12-01/gauss_counts.csv
_tmp/counts/2015-12-02/exp_counts.csv
_tmp/counts/2015-12-02/gauss_counts.csv
Which appear to be generated by:
pipeline/regtest.sh create-counts
which depends on:
Which presumably comes from having previously run:
./regtest.sh run-seq '^demo' 1 python
and not cleaning up or running any other demos (which would cause cleanup to occur) afterwards.
The text was updated successfully, but these errors were encountered: