Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I
iTasks-SDK
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 82
    • Issues 82
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 10
    • Merge Requests 10
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • clean-and-itasks
  • iTasks-SDK
  • Issues
  • #430

Closed
Open
Opened Nov 18, 2020 by Camil Staps@cstaps🚀Owner

iTasks.Extensions.Process broken on Windows

!513 (merged) seems to have introduced a bug in iTasks.Extensions.Process causing the Windows test to fail.

See:

  • https://gitlab.science.ru.nl/clean-and-itasks/iTasks-SDK/-/jobs/111787 (after !513 (merged))
  • https://gitlab.science.ru.nl/clean-and-itasks/iTasks-SDK/-/jobs/111788 (before !513 (merged))

I triggered both jobs today, so there cannot be a difference in downloaded dependencies. I had to cancel the job after !513 (merged) because the iTasks.Extensions.Process unit test does not terminate; see https://gitlab.science.ru.nl/clean-and-itasks/iTasks-SDK/-/jobs/111761 from yesterday.

Looking through the diff I don't see obvious candidates for changes that may cause this...

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: clean-and-itasks/iTasks-SDK#430