viant/endly

Error running elogger tests

dragonpiper opened this issue · 4 comments

I'm trying to run the elogger tests via endly -r=run but it fails in the log validation stage for some reason.

`[run[app]run|regresion[Prepare]exec.run 127.0.0.1:22 stdin]
rm -f /opt/elogger/logs/*
[run[app]run|regresion[Prepare]exec.run 127.0.0.1:22 stdout]

[run[app]run|regresion[Prepare]exec.run 127.0.0.1:22 stdout]

[run[app]run|regresion[Prepare] exec.run]
[run[app]run|regresion[Prepare]exec.run 127.0.0.1:22 stdin]
cd /
[run[app]run|regresion[Prepare]exec.run 127.0.0.1:22 stdout]

[run[app]run|regresion[Prepare]exec.run 127.0.0.1:22 stdin]
rm -f /opt/elogger/logs/*
[run[app]run|regresion[Prepare]exec.run 127.0.0.1:22 stdout]

[run[app]run|regresion[Prepare]exec.run 127.0.0.1:22 stdout]

[run[app]run|regresion[Prepare] validator/log.listen]
[run[app]run|regresion[Prepare]validator/log.listen unsupported scheme /opt/elogger/logs at validator/log.listen error]
[run[app]run|regresion[Prepare]validator/log.listen regresion_Prepare: unsupported scheme /opt/elogger/logs at v error]
regresion_Prepare: unsupported scheme /opt/elogger/logs at validator/log.listen at workflow.run
[run[app]run|regresion[Prepare]validator/log.listen run: regresion_Prepare: unsupported scheme /opt/elogger/logs error]
run: regresion_Prepare: unsupported scheme /opt/elogger/logs at validator/log.listen at workflow.run
[STATUS: FAILED `

Can you share your log.listen request

endly -s='validator/log' -a=listen (some valid exaples)

The problem is storage service that expect resource protocol, (i.e. file:///, scp:// etc...)
Endly uses toolbox/url/resource.go which will dynamically expand /path as file://path, so there is no need to provide proto, in log validator listen, it looks like in one place the init resource were not used but original unexpanded URL, I have applied potential patch to master,

can you provide output of the following:
endly -f=yaml -p regression/regression.csv

it should print your regression workflow model.

are you using e2e test project generator (endly -g)
or github.com/viant/endly/example/rt/elogger/e2e ?

The latter one works for me, however in the autogenerated project I have addressed one glitch,

In either case please use the latest updated endly 0.18.0 and let me know if the issue has been resolved

Check also fully functional inline workflow example
https://github.com/viant/endly/tree/master/testing/log

endly -s='validator/log' -a=listen give you example req/res and CLI documentation for validator/log

Channel info update: gophers.slack.com #endly

Just to follow up, are you still seeing any issue with testing logger?
If there is no response I will close this issue within 48 hours.