<< Back to previous view

[QB-2806] Long file removing time while building
Created: 20/Sep/16  Updated: 01/Dec/16

Status: Closed
Project: QuickBuild
Component/s: None
Affects Version/s: 5.1.16
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Bartosz Pollok Assigned To: Robin Shen
Resolution: Cannot Reproduce Votes: 0
Remaining Estimate: Unknown Time Spent: Unknown
Original Estimate: Unknown
Environment: Windows Agent on Windows Server 2008 R2.
6 core CPU, 2.6GHz, 66GB RAM


 Description   
Build step hanged nearly for 5 hours, while removing .obj files:
...
10:52:43,777 INFO - Removing file: ged_enum_interpreters.obj
15:35:59,550 INFO - Removing file: ged_enum_tables.obj
...

This situation reoccurs from time to time, but we cannot find the source of that issue: the CPU is not fully loaded then, nor memory, nor disk space.
Build just stops for couple of hours and then "unpauses" and runs further.

 Comments   
Comment by Robin Shen [ 21/Sep/16 12:32 AM ]
This sounds more like your build script issue instead of QB issue, please check your build environment.
Comment by Bartosz Pollok [ 28/Sep/16 09:42 AM ]
I did some environmental issue and it looks just fine.
Do you have any tips to find out what is happening in such cases? Any debugging methods or some verbose flag for step?
Comment by Robin Shen [ 28/Sep/16 11:16 PM ]
You may turn on debug logging to have QB print the command being executed, and then run that command from command line directly under the same working directory with same OS user to see if the problem is the same.
Comment by Bartosz Pollok [ 29/Sep/16 10:53 AM ]
Do you mean turning this logs on QB server or on the agents? Which level would you suggest DEBUG, TRACE, ALL? Current log level is set up to INFO on QB server and agents.
Currently our QB server logs are ~500MB daily, how would it increase if we change it to lower level?
Comment by Robin Shen [ 29/Sep/16 11:02 PM ]
I mean the build log level which can be specified in general setting of the configuration.
Generated at Tue May 21 23:40:23 UTC 2024 using JIRA 189.