Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Online test runner broken? #30

Open
FranklinChen opened this issue Apr 27, 2024 · 5 comments
Open

Online test runner broken? #30

FranklinChen opened this issue Apr 27, 2024 · 5 comments
Assignees
Labels
bug Something isn't working x:module/test-runner Work on Test Runners

Comments

@FranklinChen
Copy link

I tried the "hello world" exercise and although my running it offline worked, submitting it online got me

ERROR (5.2.1+00295)

Requested instance not found: 'CLIRenderer@testbox-cli'

The instance could not be located in any declared scan location(s) (/commandbox/system) or full path location
/system/wirebox/system/ioc/Injector.cfc: line 334
332: 					message = "Requested instance not found: '#arguments.name#'",
333: 					detail  = "The instance could not be located in any declared scan location(s) (#structKeyList(variables.binder.getScanLocations())#) or full path location",
334: 					type    = "Injector.InstanceNotFoundException"
335: 				);
336: 			}
called from /system/BaseCommand.cfc: line 58
called from /mnt/exercism-iteration/TestRunner.cfc: line 91
called from /mnt/exercism-iteration/TestRunner.cfc: line 47
called from /system/modules_app/task-commands/models/TaskService.cfc: line 85
called from /system/modules_app/task-commands/models/TaskService.cfc: line 322
called from /system/modules_app/task-commands/models/TaskService.cfc: line 102
called from /system/modules_app/task-commands/commands/task/run.cfc: line 68
called from /system/services/CommandService.cfc: line 345
called from /system/services/CommandService.cfc: line 158
called from /system/Shell.cfc: line 770
called from /system/Bootstrap.cfm: line 119

To enable full stack trace, run config set verboseErrors=true
Copy link

Hello. Thanks for opening an issue on Exercism 🙂

At Exercism we use our Community Forum, not GitHub issues, as the primary place for discussion. That allows maintainers and contributors from across Exercism's ecosystem to discuss your problems/ideas/suggestions without them having to subscribe to hundreds of repositories.

This issue will be automatically closed. Please use this link;%0D%0A336:%20%09%09%09%7D%0D%0Acalled%20from%20/system/BaseCommand.cfc:%20line%2058%0D%0Acalled%20from%20/mnt/exercism-iteration/TestRunner.cfc:%20line%2091%0D%0Acalled%20from%20/mnt/exercism-iteration/TestRunner.cfc:%20line%2047%0D%0Acalled%20from%20/system/modules_app/task-commands/models/TaskService.cfc:%20line%2085%0D%0Acalled%20from%20/system/modules_app/task-commands/models/TaskService.cfc:%20line%20322%0D%0Acalled%20from%20/system/modules_app/task-commands/models/TaskService.cfc:%20line%20102%0D%0Acalled%20from%20/system/modules_app/task-commands/commands/task/run.cfc:%20line%2068%0D%0Acalled%20from%20/system/services/CommandService.cfc:%20line%20345%0D%0Acalled%20from%20/system/services/CommandService.cfc:%20line%20158%0D%0Acalled%20from%20/system/Shell.cfc:%20line%20770%0D%0Acalled%20from%20/system/Bootstrap.cfm:%20line%20119%0D%0A%0D%0ATo%20enable%20full%20stack%20trace,%20run%20config%20set%20verboseErrors=true%0D%0A%60%60%60&category=cfml ) to copy your GitHub Issue into a new topic on the forum, where we look forward to chatting with you!

If you're interested in learning more about this auto-responder, please read this blog post.

@BNAndras BNAndras reopened this Apr 27, 2024
@BNAndras
Copy link
Sponsor Member

That item was moved in CommandBox 6 so that name is correct when working offline. I’ll do some digging on Monday, but I think the Docker image needs to be recompiled.

@BNAndras BNAndras self-assigned this May 17, 2024
@BNAndras BNAndras added bug Something isn't working x:module/test-runner Work on Test Runners labels May 17, 2024
@BNAndras
Copy link
Sponsor Member

@FranklinChen, sorry about the wait, but can you try again? Hopefully #34 fixed it.

@FranklinChen
Copy link
Author

Unfortunately I got the following from the simple "hello world" exercise:

Your tests timed out. This might mean that there was an issue in our infrastructure, but more likely it suggests that your code is running slowly. Is there an infinite loop or something similar?

Please check your code, and if nothing seems to be wrong, try running the tests again.

@BNAndras
Copy link
Sponsor Member

Okay, that's likely a good sign. The test runner is slow because we need to spin up CommandBox each time, and that's designed more for long-lived servers than quick one-off test runs. I'm looking into whether the new BoxLang scripting language from Ortus Solutions might be a better fit since it can natively run CFML code and hopefully be a lot faster.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working x:module/test-runner Work on Test Runners
Projects
None yet
Development

No branches or pull requests

2 participants