JuliaDebug / JuliaDebug/DebuggerFramework.jl

Pkg.test("DebuggerFramework") fails on Windows

Open
#4 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
9
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Exact error message can be found below

julia> Pkg.test("DebuggerFramework")
INFO: Computing test dependencies for DebuggerFramework...
INFO: Installing AbstractTrees v0.1.0
INFO: Installing VT100 v0.2.3
INFO: Testing DebuggerFramework
ERROR: LoadError: LoadError: UndefVarError: PTY not defined
Stacktrace:
 [1] include_from_node1(::String) at .\loading.jl:576
 [2] include(::String) at .\sysimg.jl:14
 [3] include_from_node1(::String) at .\loading.jl:576
 [4] include(::String) at .\sysimg.jl:14
 [5] process_options(::Base.JLOptions) at .\client.jl:305
 [6] _start() at .\client.jl:371
while loading C:\Users\harsha\AppData\Local\JuliaPro-0.6.2.1\pkgs-0.6.2.1\v0.6\VT100\test\TerminalRegressionTests.jl, in expression starting on line 42
while loading C:\Users\harsha\AppData\Local\JuliaPro-0.6.2.1\pkgs-0.6.2.1\v0.6\DebuggerFramework\test\runtests.jl, in expression starting on line 19
==========================[ ERROR: DebuggerFramework ]==========================

failed process: Process(`'C:\Users\harsha\AppData\Local\JuliaPro-0.6.2.1\Julia-0.6.2\bin\julia.exe' -Cx86-64 '-JC:\Users\harsha\AppData\Local\JuliaPro-0.6.2.1\Julia-0.6.2\lib\julia\sys.dll' --compile=yes --depwarn=yes --check-bounds=yes --code-coverage=none --color=yes --compilecache=yes 'C:\Users\harsha\AppData\Local\JuliaPro-0.6.2.1\pkgs-0.6.2.1\v0.6\DebuggerFramework\test\runtests.jl'`, ProcessExited(1)) [1]

================================================================================
INFO: Removing AbstractTrees v0.1.0
INFO: Removing VT100 v0.2.3
ERROR: DebuggerFramework had test errors

I tested this on both DebuggerFramework master and on latest tagged version
OS = Windows 10
Julia version = 0.6.2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with Pkg.test("DebuggerFramework") on Windows, then inspect VT100/test/TerminalRegressionTests.jl around line 42 and DebuggerFramework/test/runtests.jl around line 19. Trace why PTY is undefined on Windows and verify that the DebuggerFramework test suite completes successfully there.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
operating-systems, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.