Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Failed compilations always report 0.000 seconds

Open
#37 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Shivangi-singh18 is already working on this.

Since Oct 11, 2026.

  • #42 by @Shivangi-singh18 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp, python
Domain
backend

Research direction

Read the compilation runner code that records and reports elapsed time, then trace the failed compilation path using the C++ example described in the issue. Reproduce a compilation error that takes several seconds and check where the reported duration becomes 0.00s; done means failed compilations report their actual elapsed time.

Written by the indexing model from the issue text.

Description

I noticed that when compilation fails, the runner always reports an elapsed time of 0.0 seconds, even if compilation takes several seconds.

I tested this with a C++ program containing a compilation error, and it took more than 3-4 seconds to fail.

The runner should report the actual compilation time for failed compilations as a normal behaviour but it always gives 0.00s.

Dominant language
Python
Stars
1
Forks
6
Avg merge
17h 52m
Merged PRs (30d)
14

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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.

More from techcsispit/code-corner

All issues in techcsispit/code-corner

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.