NatLabRockies / NatLabRockies/OpenStudio

Investigate why sqlfile tests are failing the first time on a clean build

Open
#4,608 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component - Testing Continuous Integration Developer Issue
Dominant language
C++
Stars
646
Forks
237
Avg merge
3d 11h
Merged PRs (30d)
10

Description

Issue overview

There's something sequential or relying on a previous test likely, as they will pass the second time they run.

The following tests FAILED:
	167 - SqlFileFixture.TimeSeriesValues (Failed)
	168 - SqlFileFixture.TimeSeriesCount (Failed)
	169 - SqlFileFixture.TimeSeries (Failed)
	170 - SqlFileFixture.BadStatement (Failed)
	171 - SqlFileFixture.CreateSqlFile (Failed)
	172 - SqlFileFixture.AnnualTotalCosts (Failed)
	173 - SqlFileFixture.Regressions (Failed)
	174 - SqlFileFixture.SqlFile_LeapYear (Failed)
	175 - SqlFileFixture.SqlFile_Escapes_injection (Failed)
	176 - SqlFileFixture.EndUseFuelTypes_test (Failed)
	177 - SqlFileFixture.4298_YearField (Failed)

Details

Environment

Some additional details about your environment for this issue (if relevant):

  • Platform (Operating system, version): all (I did notice both Ubuntus at least)
  • Version of OpenStudio (if using an intermediate build, include SHA): 1164fb61b4a6f3614edd936512e61560dea415df
Context

Contributor guide

Open the 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.

Research direction

Start by running the listed SqlFileFixture tests on a clean build, then run them again to compare the failures. Investigate the shared setup or ordering behind TimeSeriesValues through 4298_YearField, and confirm the fix by making the full first run pass without relying on a previous test run.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.